On Mon, May 16, 2011 at 07:28:42PM +0300, saeed bishara wrote: > > I think you need to lay out exactly what you want/need done here, as it > > sounds like both a lot of different things, and pretty vague. > > > > Do you want to go through the above tree and look at the diff and pick > > the different pieces out, or do you want me to do that and ask you about > > all of them? > Greg, it very big list, our patch touches ~1000 files. > I think I should prepare a list of the following: > 1. new drives that need to be written from scratch > 2. missing features for the existing drivers > 3. arch-specific missing features. Yes, please write this out in detail so that we know what is needed to be accomplished. > the tree above will be used by developers as a reference only. I don't > think it's practical to rebase it to recent kernels or to do direct > work on it. does that answers your question? Starting with older, working code, is always easier than writing new stuff from nothing, right? > > Also, how can I get a sample device to test that I don't break anything? > sure, we will send you one. Ok, I'll send you my address off-list. thanks, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
