On Thu, 24 Feb 2005, Manu Abraham wrote: > Martin Cap wrote: >> Hi, >> >> I am having the similar issues with kernel oops. Check my postings with the >> title "[PATCH] Twinhan...oops" here in the mailing-list. >> > > Martin, > > I saw your post, i am looking at that code only. It is not quite easy with > one single driver handling around 13 ~ 15 cards and each card has again > branched firmware versions, most of them looking similar and slight > difference in firmware versions, again FTA/CI, on Sat/Cab/Terr/ATSC and with > all kinds of CI modules from all vendors, some adhering to some standards, > some not adhering to any standards at all. > > > When getting things like that together, one can expect a little bit of > hiccups. Maybe it would be easier for users, if they wouldn't need to patch existings trees. Manu, maybe should get an dvb-kernel CVS account and start a temporary directory (like I did for b2c2 flexcop devices). With all patched files inside and an independent build-scheme. IMHO it would be easier for the user to test your latest changes, thus you would reach a wider test community. You also would be able to put special load-scripts, with all necessary parameters for the users to debug. regards, Patrick. -- Mail: patrick.boettcher@xxxxxxx WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
