On Wed, Dec 03, 2008 at 09:48:18PM -0600, Jon Elson wrote: > Peter C. Wallace wrote: > > > > As I said before maybe the way to ease into this is just support 1 or a few > > Ethernet chips, and require the user to have a add-in PCI/PCIe Ethernet card > > with the required chip. > > > Having fought this problem to some extent with the par port, I can't > IMAGINE the headache when a potential customer shows up and you tell him > "Oh, it only works on computers with a DEC Tulip ethernet chip." Add, > he says, "How do I tell, sight unseen, whether any particular computer > has that specific chip?" > No, it has to have a bit wider hardware support to be viable.
I think the answer is explicitly in what Peter said above. You don't care what comes in the computer. You point them to a particular network card because it has the right chipset. It'll be about $5. Heck, you might say, as someone who sells hardware that works with it, you'll just send him one off your stack of them. They're $5, after all. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
