Ok, this is the 3rd revised patch for PnP. I think it works
fairely well.
I may not invest further time on this, now that ACPI is
taking over device configuration business... :-)
Kazu
>> I once wrote the following patch to deal with this problem by
>> probing ISA devices in the following order
>> I once wrote the following patch to deal with this problem by
>> probing ISA devices in the following order.
>>
>> 1. sensitive ISA devices described in device.hints
>> 2. PnP BIOS ISA devices
>> 3. other ISA devices described in device.hints
>> 4. PnP ISA devices
>
>This order is still sligh
Mike Smith <[EMAIL PROTECTED]> wrote:
> > It's written for 4.X, but might work for -current (you'll have to
> > disable the checks for 4.X, at the very least). You use it like this:
> >
> > dmesg | scanirq
>
> It's completely obsoleted by devinfo and pciconf's '-v' flag.
>
> Sorry. 8)
> I remember an ACER system with a bus mouse on the motherboard
> which was unknown to the PnP BIOS, and Windows 95 trying to
> be a "PnP OS" used to always do what above looks to be the
> "PnP ISA devices" phase of things, and gave IRQ 12 to the
> second IDE disk interface, instead of the on-boar
> I once wrote the following patch to deal with this problem by
> probing ISA devices in the following order.
>
> 1. sensitive ISA devices described in device.hints
> 2. PnP BIOS ISA devices
> 3. other ISA devices described in device.hints
> 4. PnP ISA devices
This order is still slightly wrong.
Warner Losh wrote:
> : Whether it's perfect or not, making the device.hints "go away"
> : in the presents of PnP BIOS on the machine would seem to be
> : able to address the issue of doubled entries... right?
>
> Not entirely. There are ISA devices in devices.hints that aren't plug
> and play an
>
> > Then go look them up. I'm not about to stuff the entire PnP device
> > database into the kernel just to satisfy your curiosity. 8(
>
> I was going to ask where, but I see they are in
> /usr/src/sys/boot/common/pnpdata.
That's a useful subset that I keep forgetting about; thanks for remi
>: Whether it's perfect or not, making the device.hints "go away"
>: in the presents of PnP BIOS on the machine would seem to be
>: able to address the issue of doubled entries... right?
>
>Not entirely. There are ISA devices in devices.hints that aren't plug
>and play and aren't in the PnP BIOS
> Then go look them up. I'm not about to stuff the entire PnP device
> database into the kernel just to satisfy your curiosity. 8(
I was going to ask where, but I see they are in
/usr/src/sys/boot/common/pnpdata.
thanx,
brad
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe f
> I think the reason the hints are not just ignored is to allow
> people to fix "rogue" hardware. I'm willing to be corrected,
Good. It's like it is right now because the PnP stuff was bolted on as
an afterthought.
> since this looks like about 12 lines of code would make it
> ignore device.h
In message <[EMAIL PROTECTED]> Terry Lambert writes:
: Warner Losh wrote:
: > Since that's not how it works, the solution is a non-starter.
: >
: > We just need to carefully order the ISA code probing sections to get
: > the desired effects. We haven't done that yet. All PnP devices are
: > pro
Warner Losh wrote:
> Since that's not how it works, the solution is a non-starter.
>
> We just need to carefully order the ISA code probing sections to get
> the desired effects. We haven't done that yet. All PnP devices are
> probed together at the end, which isn't quite right.
The problem wa
Mike Smith wrote:
> > So, you are saying that this is because there is not a seperate
> > "No BIOS" and "BIOS" section (or entry prefix) in the hints file,
> > so that in a non-PnP system, both the "No BIOS" and "BIOS"
> > entries will be examined, whereas on a PnP system, only the "BIOS"
> > entr
In message <[EMAIL PROTECTED]> Terry Lambert writes:
: So, you are saying that this is because there is not a seperate
: "No BIOS" and "BIOS" section (or entry prefix) in the hints file,
: so that in a non-PnP system, both the "No BIOS" and "BIOS"
: entries will be examined, whereas on a PnP syste
Warner Losh wrote:
> : Shouldn't we just take the Linux/NetBSD information, and
> : actually identify the things instead of saying "Unknown",
> : instead, and leave them printing to encourage someone the
> : messages annoy to do the work?
>
> I'd guess that's too much work. Maybe someone can pro
> So, you are saying that this is because there is not a seperate
> "No BIOS" and "BIOS" section (or entry prefix) in the hints file,
> so that in a non-PnP system, both the "No BIOS" and "BIOS"
> entries will be examined, whereas on a PnP system, only the "BIOS"
> entries will be examined?
This
> > >: unknown: can't assign resources
> > >: unknown: can't assign resources
> > >: unknown: can't assign resources
> > >: unknown: can't assign resources
> > >: unknown: can't assign resources
> > >: unknown: can't assign resources
> > >
> > >Don't worry about these.
> >
> > Shouldn't we
Kazutaka YOKOTA wrote:
> Um, we see these messages not only because our ISA PnP driver needs
> some update, but also because we create ISA device instances TWICE for
> each motherboard ISA devices, such as sio and atkbdc, due to
> /boot/device.hints.
>
> We need to have /boot/device.hints for tho
Thus spake Warner Losh ([EMAIL PROTECTED]):
> I'd guess that's too much work. Maybe someone can prove me wrong with
> trivial patches.
Maintaining the device-table is probably the most work (since
we already have the PNP string and most lists are sortedc
by this string as well).
Alex
To
In message <[EMAIL PROTECTED]> Terry Lambert writes:
: Shouldn't we just take the Linux/NetBSD information, and
: actually identify the things instead of saying "Unknown",
: instead, and leave them printing to encourage someone the
: messages annoy to do the work?
I'd guess that's too much work.
Kazutaka YOKOTA wrote:
> >: I'm running -current as of an hour ago. I've gotten this since I've
> >: been running 4.2-stable, any ideas on how I can find out what it
> >: belongs to?
> >:
> >: unknown: can't assign resources
> >: unknown: can't assign resources
> >: unknown: can't assign resou
In message <[EMAIL PROTECTED]> Wilko Bulte writes:
: They are also in RELENG_4..
Those should be hidden by -v then :-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>
> >: unknown: can't assign resources
> >: unknown: can't assign resources
> >: unknown: can't assign resources
> >: unknown: can't assign resources
> >: unknown: can't assign resources
> >: unknown: can't assign resources
>
> > Shouldn't we just suppress the message? It just confuses us
>In message <[EMAIL PROTECTED]> Kazutaka YOK
>OTA writes:
>: Shouldn't we just suppress the message? It just confuses users.
>:
>: The attached patch will print this message only when we boot
>: the kernel by 'boot -v'.
>
>They are there to remind certain folks that the ISA PnP code is broken
On Sun, Aug 26, 2001 at 09:51:57AM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Kazutaka YOKOTA
>writes:
> : Shouldn't we just suppress the message? It just confuses users.
> :
> : The attached patch will print this message only when we boot
> : the kernel by 'boot -v'.
>
> They
>: unknown: can't assign resources
>: unknown: can't assign resources
>: unknown: can't assign resources
>: unknown: can't assign resources
>: unknown: can't assign resources
>: unknown: can't assign resources
> Shouldn't we just suppress the message? It just confuses users.
I would be s
In message <[EMAIL PROTECTED]> Kazutaka YOKOTA
writes:
: Shouldn't we just suppress the message? It just confuses users.
:
: The attached patch will print this message only when we boot
: the kernel by 'boot -v'.
They are there to remind certain folks that the ISA PnP code is broken
slightly
>In message <[EMAIL PROTECTED]> "David W. Chapman
> Jr." writes:
>: I'm running -current as of an hour ago. I've gotten this since I've
>: been running 4.2-stable, any ideas on how I can find out what it
>: belongs to?
>:
>: unknown: can't assign resources
>: unknown: can't assign resources
> Going off on a slight tangent, I wrote a perl script months ago
> that parsed the output of dmesg, and tried to determine which IRQs were
> used, and for what. One of the side-effects of this script is that it
> also tried to identify unknown PCI devices (but *only* if an IRQ is
> used), u
In message <[EMAIL PROTECTED]> "David W. Chapman Jr."
writes:
: I'm running -current as of an hour ago. I've gotten this since I've
: been running 4.2-stable, any ideas on how I can find out what it
: belongs to?
:
: unknown: can't assign resources
: unknown: can't assign resources
: unknow
Alexander Langer <[EMAIL PROTECTED]> wrote:
> Thus spake David W. Chapman Jr. ([EMAIL PROTECTED]):
>
> > I'm running -current as of an hour ago. I've gotten this since I've
> > been running 4.2-stable, any ideas on how I can find out what it
> > belongs to?
>
> Statically wired ISA devices.
Thus spake David W. Chapman Jr. ([EMAIL PROTECTED]):
> I'm running -current as of an hour ago. I've gotten this since I've
> been running 4.2-stable, any ideas on how I can find out what it
> belongs to?
Statically wired ISA devices.
> unknown: can't assign resources
> unknown: can't assig
"David W. Chapman Jr." <[EMAIL PROTECTED]> is believed to have written:
> On Fri, Aug 24, 2001 at 01:13:36AM +0200, Salvo Bartolotta wrote:
> > > I'm running -current as of an hour ago. I've gotten this since I've
>
> > > been running 4.2-stable, any ideas on how I can find out what it
> > > b
On Fri, Aug 24, 2001 at 01:13:36AM +0200, Salvo Bartolotta wrote:
> > I'm running -current as of an hour ago. I've gotten this since I've
> > been running 4.2-stable, any ideas on how I can find out what it
> > belongs to?
>
> > unknown: can't assign resources
> > unknown: can't assign resou
> I'm running -current as of an hour ago. I've gotten this since I've
> been running 4.2-stable, any ideas on how I can find out what it
> belongs to?
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
> u
I'm running -current as of an hour ago. I've gotten this since I've
been running 4.2-stable, any ideas on how I can find out what it
belongs to?
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown: can't a
36 matches
Mail list logo
