Messages in this thread | | | Subject | RE: Digi Neo 8: linux-2.6.12_r2 jsm driver | Date | Tue, 12 Apr 2005 11:42:31 -0500 | From | "Kilau, Scott" <> |
| |
Hi Jan,
> But please be prepared to be in a competitive position. You've won't get > your driver included by just telling once about it; you'll need to work > towards that goal, and probably monitor the driver to be useable in the > future.
The JSM driver is a "stripped" down version of the DGNC driver.
There is no "competition" between these 2 drivers. They were always intended to work side by side with each other.
Both drivers will get all fixes/changes added to them at the same time, since 90% of the driver code is the same.
The JSM driver was forced to be stripped down when being submitted to the kernel sources, and many extended features removed as so to be included into the kernel, as the extended features added special ioctls and special /proc (/sys for 2.6) files.
Oddly enough, I have had a few of our customers come back to me, after seeing some of the previous JSM threads about yanking the extended features, and I quote:
> I didn't think that you would remove them. I read the posts and > wondered *why* they wanted the management pieces removed. > One reason to use the Digi products is for the sole fact that > they *can* be diagnosed. > I'm glad that Digi is still focused properly. > I agree that committing the drivers to the main kernel > is not the way to go if you are forced to remove dpa and ditty.
But this is neither here nor there, as Christoph has made it clear, actual "Digi customers" don't matter.
I will let the chips fall where they will, and clean up the mess that will soon be introduced into my driver world. =)
Scott
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |