> From: Jeff Garzik [mailto:[EMAIL PROTECTED]]
>
> On Mon, 25 Sep 2000, Dan Hollis wrote:
> > On Mon, 25 Sep 2000, Jeff Garzik wrote:
> > > I see you suggestion in the same way... If we keep the
> PCI device name
> > > data around after boot, then we have a lot of kernel
> memory locked up
>
>
> On Mon, 25 Sep 2000, Andrzej Krzysztofowicz wrote:
> > I mean moving the __init database compiled into kernel (based on pci.ids) to
> > a separate module, which would be responsible for on-demand updating of text
> > information (i.e. replacing VID:DID numbers with text).
>
> In early
On Mon, 25 Sep 2000, Dan Hollis wrote:
> On Mon, 25 Sep 2000, Jeff Garzik wrote:
> > I see you suggestion in the same way... If we keep the PCI device name
> > data around after boot, then we have a lot of kernel memory locked up
> > on the off chance that a HotPlug PCI device might appear for
On Mon, 25 Sep 2000, Jeff Garzik wrote:
> I see you suggestion in the same way... If we keep the PCI device name
> data around after boot, then we have a lot of kernel memory locked up
> on the off chance that a HotPlug PCI device might appear for which we
> need a name.
> I would much prefer a
On Mon, 25 Sep 2000, Andrzej Krzysztofowicz wrote:
> I mean moving the __init database compiled into kernel (based on pci.ids) to
> a separate module, which would be responsible for on-demand updating of text
> information (i.e. replacing VID:DID numbers with text).
In early 2.3.x, the fbdev
>
> On Mon, 25 Sep 2000 11:07:58 +0200 (CEST),
> Andrzej Krzysztofowicz <[EMAIL PROTECTED]> wrote:
> >BTW, what do you think of idea making the pci.ids base modular ?
> >The module while loading should process the queue.
>
> Does the modules.pcimap file creates by recent modules do what you
>
On Mon, 25 Sep 2000, Andrzej Krzysztofowicz wrote:
> BTW, what do you think of idea making the pci.ids base modular ?
> I mean replacing data requests from pci.ids base by their queuing requests
> (+ eventually request_module(pci_ids) to process the queue if possible )
>
> The module while
On Mon, 25 Sep 2000 11:07:58 +0200 (CEST),
Andrzej Krzysztofowicz <[EMAIL PROTECTED]> wrote:
>BTW, what do you think of idea making the pci.ids base modular ?
>The module while loading should process the queue.
Does the modules.pcimap file creates by recent modules do what you
want? It maps
On Mon, 25 Sep 2000 11:07:58 +0200 (CEST),
Andrzej Krzysztofowicz [EMAIL PROTECTED] wrote:
BTW, what do you think of idea making the pci.ids base modular ?
The module while loading should process the queue.
Does the modules.pcimap file creates by recent modules do what you
want? It maps PCI
On Mon, 25 Sep 2000, Andrzej Krzysztofowicz wrote:
BTW, what do you think of idea making the pci.ids base modular ?
I mean replacing data requests from pci.ids base by their queuing requests
(+ eventually request_module(pci_ids) to process the queue if possible )
The module while loading
On Mon, 25 Sep 2000 11:07:58 +0200 (CEST),
Andrzej Krzysztofowicz [EMAIL PROTECTED] wrote:
BTW, what do you think of idea making the pci.ids base modular ?
The module while loading should process the queue.
Does the modules.pcimap file creates by recent modules do what you
want? It
On Mon, 25 Sep 2000, Andrzej Krzysztofowicz wrote:
I mean moving the __init database compiled into kernel (based on pci.ids) to
a separate module, which would be responsible for on-demand updating of text
information (i.e. replacing VID:DID numbers with text).
In early 2.3.x, the fbdev
On Mon, 25 Sep 2000, Jeff Garzik wrote:
I see you suggestion in the same way... If we keep the PCI device name
data around after boot, then we have a lot of kernel memory locked up
on the off chance that a HotPlug PCI device might appear for which we
need a name.
I would much prefer a
13 matches
Mail list logo
