-On [2119 08:00], Warner Losh ([EMAIL PROTECTED]) wrote:
>In message <[EMAIL PROTECTED]> Chris Piazza writes:
>: I *thought* I noticed it was different. I actually find this pretty
>: annoying because it wraps almost all of the lines and makes it difficult
>: to read dmesg.
>
>I don't mind th
> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> was assigned. A single line should be
On Wed, 19 Jan 2000, David Scheidt wrote:
> On Wed, 19 Jan 2000, Andrzej Bialecki wrote:
>
> >
> > I did some hacks a while ago on a tool which could be called "devinfo". It
> > simply traversed the dev/bus tree and displayed tons of info about each
> > node.
> >
> > Perhaps something like tha
On Wed, 19 Jan 2000, Andrzej Bialecki wrote:
>
> I did some hacks a while ago on a tool which could be called "devinfo". It
> simply traversed the dev/bus tree and displayed tons of info about each
> node.
>
> Perhaps something like that could be useful instead of full-blown FS?
This is somet
On Tue, 18 Jan 2000, Matthew N. Dodd wrote:
> On Wed, 19 Jan 2000, Poul-Henning Kamp wrote:
> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
> >
> > Is this level of verbosity really helping anybody ?
>
> Its consistant, but I need to
> The IRQ is useful to me at least, since the ISA/PCI irq distribution is
> rather hackish and non-trivial to get right at times.
Note that I'm not saying that IRQ is not useful - I'm just asking whether it's
important to see when bootverbose == 0.
To Unsubscribe: send mail to [EMAIL PROTECT
In message <[EMAIL PROTECTED]>, Matthew
Jacob writes:
>
>
>> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
>> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>>
>> Agreed. For a PCI card all I want to know is what i
In message <[EMAIL PROTECTED]> Chris Piazza writes:
: I *thought* I noticed it was different. I actually find this pretty
: annoying because it wraps almost all of the lines and makes it difficult
: to read dmesg.
I don't mind them, but wouldn't object to a generic wrapping
mechanism.
Warner
On Tue, 18 Jan 2000, David O'Brien wrote:
> On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote:
> > > Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> > > was assigned. A single line should be suffient.
> >
> > Do you even need to know what IRQ it was assig
>
> What would be nice would be to have the normal version displayed and
> the verbose stuff go to a seperate buffer and logged seperatly..
>
> ie so you don't clutter your boot screen with junk, but if you have a
> problem you can get at the verbose info :)
>
> .. and no I don't have any patc
On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote:
> > Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> > was assigned. A single line should be suffient.
>
> Do you even need to know what IRQ it was assigned? It seems to me that IRQ,
With wacky PC hardwar
On 19-Jan-00 Matthew Jacob wrote:
> Do you even need to know what IRQ it was assigned? It seems to me
> that IRQ,
> like IO-PORT, is only needed if you're either interested in such
> stuff or to
> catch conflicts (both are under bootverbose)
What would be nice would be to have the normal ve
> On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
> > fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Agreed. For a PCI card all I want to know is what it is, and what IRQ it
> was assigned. A single line should b
On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
Agreed. For a PCI card all I want to know is what it is, and what IRQ it
was assigned. A single line should be suffient.
>
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Is this level of verbosity really helping anybody ?
>
> I thought we printed out the port/mem stuff for ISA because it is
> usually jumpered by the admin, but for dynamic allocation
On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote:
>
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Is this level of verbosity really helping anybody ?
I *thought* I noticed it was different. I actually find this p
On Wed, 19 Jan 2000, Poul-Henning Kamp wrote:
> fxp0: port 0xc400-0xc43f mem
>0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
>
> Is this level of verbosity really helping anybody ?
Its consistant, but I need to unify all the resource printing stuff since
theres about
fxp0: port 0xc400-0xc43f mem
0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0
Is this level of verbosity really helping anybody ?
I thought we printed out the port/mem stuff for ISA because it is
usually jumpered by the admin, but for dynamic allocation busses/devices
18 matches
Mail list logo
