David Campbell (email@example.com)
Mon, 19 Oct 1998 17:53:54 +0800
From: Philip Blundell <firstname.lastname@example.org>
> Obviously this doesn't quite work if you have more than
> one type of parallel port, but only about one user in a million is in that
> situation and they can sort it out for themselves. :-)
Forward all problems related to forgetting to load parport modules to Phil.
I can assure you that it isn't the "one user in a million". I can also assure you
that it is possible to build a kernel without low level parport support. Perhaps
we need #define sequence to kill the kernel compile if the user forgot to
select parport_pc (or similar) even as a module. I myself have been caught a
several times by this one. Perhaps we need to edit the Config.in file to force
parport_pc to be modularised by default.
#error No low level parport driver specified.
BTW: When coding parport-scsi I chose not to have *another* core module.
Currently with ppa you require the following:
Just to get to the ZIP disk, this doesn't count "vfat" as a module. I didn't think
another module would go down well.
Appologies for being a bit abrasive here but completely rewriting drivers
(almost from scratch) does that to me...
Current project list:
a) Maintain Linux ZIP drivers (documentation needed)
b) Create Linux chipset specific parport drivers
c) Start on ParSCSI drivers (75% complete)
Any assistance to clearing this list most welcome
-- To unsubscribe, send mail to: email@example.com --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Wed 30 Dec 1998 - 10:18:37 EST