Andrew Morton wrote:
> On Sat, 02 Sep 2006 13:15:52 +0200
> Pierre Ossman <[email protected]> wrote:
>
>> Andrew, we could use some help with how this driver should fit into the
>> kernel tree. The hardware is multi-function, so there will be a couple
>> of drivers, one for every function, and a common part. How has this been
>> organised in the past?
>>
>>
>
> Greg would be a far better person that I for this. Is it a PCI device?
>
It's always difficult to know who to contact when there's an issue that
isn't specific to one single area. And since you are the 2.6 maintainer
I figured it wouldn't be too off base to throw this in your lap. ;)
This is a PCI device yes. Which has a number of card readers as
separate, hot-pluggable functions. Currently this means it interacts
with the block device and MMC subsystems of the kernel. As more drivers
pop up, the other card formats will probably get their own subsystems
the way MMC has. So there are three issues here:
* Where to put the central module that handles the generic parts of the
chip and pulls in the other modules as needed.
* If the subfunction modules should be put with the subsystems they
connect to or with the main, generic module.
Rgds
Pierre
--
VGER BF report: H 0.055417
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
