From: Jeff Garzik <jgarzik@pobox.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Adam Belay <ambx1@neo.rr.com>,
"torvalds@transmeta.com" <torvalds@transmeta.com>,
"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>,
"greg@kroah.com" <greg@kroah.com>,
"jdthood@yahoo.co.uk" <jdthood@yahoo.co.uk>,
"boissiere@nl.linux.org" <boissiere@nl.linux.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PnP Layer Rewrite V0.7 - 2.4.42
Date: Mon, 14 Oct 2002 15:22:52 -0400 [thread overview]
Message-ID: <3DAB198C.4030709@pobox.com> (raw)
In-Reply-To: Pine.LNX.4.33.0210142101000.7202-100000@pnote.perex-int.cz
Jaroslav Kysela wrote:
> On Mon, 14 Oct 2002, Adam Belay wrote:
>
>
>>Linux Plug and Play Rewrite V0.7
>>
>>After much testing the Linux PnP Rewrite is ready to be included. For
>>those who would like to try it, be sure to enable debugging or else it
>>will operate silently. Also enable both PnP protocols.
>
>
> A few notes. Please, could you leave the raw proc interface for ISA PnP?
If a rewrite is being done, there are a lot better ways to do this than
via ->proc_read and ->proc_write... plus overall procfs usage should be
deprecated where reasonable/possible...
> I mean isapnp_proc_bus_read() function. Also, encoding device/vendor to
> 7-byte string seems like wasting bytes and CPU cycles. If you use 2/2 byte
> format, you'll spare 3 bytes and comparing of two short values (or one
> int value) is always less expensive.
ASCII has always been preferred. google for "Linus", "linux-kernel",
and "ASCII" to see Linus's several postings on the subject...
> Anyway, I like this code. It seems that you don't use standard pci_dev /
> pci_bus structures as I was forced by Linus at ISA PnP code inclusion
> time. But it's true that we have new device model, so these things might
> be private. Also, don't forget to remove additional ISA PnP members from
> pci structures when Linus approves pnp_dev and pnp_card structures.
agreed.
Regards,
Jeff
next prev parent reply other threads:[~2002-10-14 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021014135452.GB444@neo.rr.com>
2002-10-14 18:10 ` [PATCH] PnP Layer Rewrite V0.7 - 2.4.42 Greg KH
2002-10-15 16:09 ` Adam Belay
2002-10-15 20:32 ` Greg KH
2002-10-14 19:10 ` Jaroslav Kysela
2002-10-14 19:22 ` Jeff Garzik [this message]
2002-10-14 21:43 ` Adam Belay
2002-10-15 3:13 ` Greg KH
2002-10-15 15:36 ` Thomas Hood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DAB198C.4030709@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ambx1@neo.rr.com \
--cc=boissiere@nl.linux.org \
--cc=greg@kroah.com \
--cc=jdthood@yahoo.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.