Marcel Moolenaar wrote: > > On Oct 27, 2007, at 4:01 PM, Erik Trulsson wrote: > >> On Sat, Oct 27, 2007 at 03:09:38PM -0700, Marcel Moolenaar wrote: >>> >>> On Oct 27, 2007, at 2:42 PM, Erik Trulsson wrote: >>> >>>> On Sat, Oct 27, 2007 at 12:09:29PM -0700, Marcel Moolenaar wrote: >>>>> >>>>> On Oct 27, 2007, at 10:58 AM, John-Mark Gurney wrote: >>>>> >>>>>> Yeh, you're solution was to simply declare that anyone who knows that >>>>>> COM1 is at 0x3f8 is wrong, and to use a different, yet again >>>>>> arbitrary >>>>>> solution which is which is listed first in ACPI... >>>>> >>>>> Exactly. Anyone who "knows" that COM1 is at 0x3f8 while >>>>> the computer right in front of them clearly states that >>>>> COM1 is at 0x2f8 is in denial. >>>> >>>> If I say in the BIOS setup screen that the first serial port is >>>> to use 0x3f8, then that is the port which I want sio0 to attach to, >>>> regardless of in which order FreeBSD sees them enumerated. >>> >>> What is the first serial port in the BIOS? >> >> It is the port which is labeled 'Serial Port 1' or something similar. > > I see. Some argue it's the UART at port 0x3f8, because > that's how things have been documented. I like your > definition, but unfortunately this thread is mostly > about how we want sio0 at a fixed port by virtue of > hints. > >>> Is that not the one >>> that's enumerated first? >> >> Not necessarily, no. It should be, but is not always. > > Ok. What's buggy if it's not -- ACPI? > >> BIOSs are fairly often buggy or get things wrong. Being able to override >> the BIOS when it is wrong is a Good Thing. > > I would presume that we can patch the AML if it's an ACPI > problem. That seems to me to be the right thing to do: > you patch what is broken... I'd argue that com0 is the one that windows calls com1 >Received on Sun Oct 28 2007 - 01:34:34 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:20 UTC