Date: Thu, 20 Aug 1998 21:19:58 +0200 (CEST) From: Søren Schmidt <sos@FreeBSD.org> To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Cc: wpaul@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/pci if_xl.c Message-ID: <199808201919.VAA03438@sos.freebsd.dk> In-Reply-To: <xzpiujnad0l.fsf@skejdbrimir.ifi.uio.no> from =?ISO-8859-1?Q?Dag=2DErling_Coidan_Sm=F8rgrav?= at "Aug 20, 98 03:28:26 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Dag-Erling Coidan Smørgrav who wrote:
>
> Hmm, speaking of longer-than-80-col, I have a few PCI devices (Adaptec
> 2940UW SCSI controller, Intel EtherExpress 100B LAN controller, 3Com
> Etherlink XL LAN controller) that have names so long the probe message
> is longer than 80 columns. Could the "int x irq x on pcix.xx.x" stuff
> be written out on a separate line to avoid this?
>
> Here's an example:
>
> xl0: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on pci0.1
> 7.0
>
> should IMHO be
>
> xl0: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00
> xl0: int a irq 11 on pci0.17.0
I vote for as short and few messages as possible, one should boot
with -v to get the longish more descriptive version.
Ideally one line pr device thats it.
Try boot a fairly new linux kernel and see what it can be driven
to if not kept short, you almost know the name of the developers
dog from that :)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
Even more code to hack -- will it ever end?
..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808201919.VAA03438>