[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061214182626.6b07c6ad@localhost.localdomain>
Date: Thu, 14 Dec 2006 18:26:26 +0000
From: Alan <alan@...rguk.ukuu.org.uk>
To: Greg KH <gregkh@...e.de>
Cc: Hans-J??rgen Koch <hjk@...utronix.de>,
Hua Zhong <hzhong@...il.com>,
"'Martin J. Bligh'" <mbligh@...igh.org>,
"'Linus Torvalds'" <torvalds@...l.org>,
"'Jonathan Corbet'" <corbet@....net>,
"'Andrew Morton'" <akpm@...l.org>,
"'Michael K. Edwards'" <medwards.linux@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches
for 2.6.19]
> Think of uio as just a "class" of driver, like input or v4l. It's still
> up to the driver writer to provide a proper bus interface to the
> hardware (pci, usb, etc.) in order for the device to work at all.
Understood. That leads me to ask another question of the folks who deal
with a lot of these cards. How many could reasonably be described by the
following
bar to map, offset, length, ro/rw, root/user, local-offset
(x n ?)
interrupt function or null
It seems if we have a lot of this kind of card that all fit that pattern
it might actually get more vendors submitting updates if we had a single
pci driver that took a struct of the above as the device_id field so
vendors had to write five lines of IRQ code, a struct and update a PCI
table ? That seems to have mostly worked with all the parallel/serial
boards.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists