From: Greg KH <greg@kroah.com>
To: wdebruij@dds.nl
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [ANNOUNCE] various linux kernel devtools : device handling/memory mapping/profiling/etc.
Date: Mon, 5 Apr 2004 11:23:04 -0700 [thread overview]
Message-ID: <20040405182304.GA8008@kroah.com> (raw)
In-Reply-To: <1081186402.407198620a28b@webmail.dds.nl>
On Mon, Apr 05, 2004 at 07:33:22PM +0200, wdebruij@dds.nl wrote:
> - a generic device file interface, which abstracts away kernelversion
> differences, devfs/mknod/udev differences and memory addressing differences.
I don't see anything in there that will work properly for udev. Am I
just missing the code somewhere? Remember, for udev to work, you have
to create stuff in sysfs, which I don't see this code doing.
> - a generic pci initialization interface. Could perhaps be merged with the
> existing PCI subsytem. I needed it for implementing a PCI driver (more below)
Ick, you are using pci_find_device() which is racy, depreciated, and
does not play nice with the rest of the kernel. Yes, it's the lowest
common denominater accross 2.2, 2.4, and 2.6, but please don't sink to
that level if you don't have to. For 2.6 it's just not acceptable.
I agree that at times the current kernel driver api learning curve is a
bit steep. But people are working to reduce that curve where they can,
and it's one of my main priorities for 2.7. Any help and suggestions
that you might have in that area are greatly appreciated.
thanks,
greg k-h
next prev parent reply other threads:[~2004-04-05 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 17:33 [ANNOUNCE] various linux kernel devtools : device handling/memory mapping/profiling/etc wdebruij
2004-04-05 18:23 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 19:00 wdebruij
2004-04-05 19:30 ` Greg KH
2004-04-06 11:55 ` Willem de Bruijn
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=20040405182304.GA8008@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wdebruij@dds.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox