On Mon, 2019-10-07 at 09:23 +0200, Hannes Reinecke wrote: > On 10/7/19 9:02 AM, Mischa Baars wrote: > > On Sun, 2019-10-06 at 09:10 -0600, Jens Axboe wrote: > [ .. ] > > > I'm saying that you are comparing apples to oranges. The floppy driver > > > might be older tech, but it's much more used than pktcdvd. It's not the > > > case that we must pick one over the other, in terms of what stays and > > > what goes. > > > > > > > Yes we are, sort of. You can even have my pear. That's exactly the problem with your story :) > > > > A DVD is 4Gb and Blueray goes all the way up to 100Gb, while a floppy disc is 1.44Mb. > > Who would want to write his backup files to 1.44Mb floppy disc these days? > > > Why do you keep on bringing up floppy? > I was under the impression that you wanted to use pktdvd, not floppy... > And as Jens made it clear, any potential removal of the floppy driver > will have _zero_ influence on the future of pktdvd. I do not keep bringing up the floppy drives. I'm merely trying to point out that removing the floppy driver is the more logical course of action. Also, you must be mistaken. It's not about the potential removal of the floppy driver, it's about the removal of the packet writing driver. There will be no pktcdvd kernel module in the future. To be precise, both reading and writing dvd's is already unsupported in the latest linux-next kernel. > And in either case, the main question here was: > Will you rebase your project to latest mainline once it's ready? > Or will you settle on a kernel version to do your development on, and > continue using that for your project? No, the code is intended for companies like AMD, Intel or ARM. It is not indended for the opensource community. Does that mean that I cannot develop on an opensource platform? Is that you are trying to tell me? > Incidentally: I _do_ know of one company who happily will provide you > with a stable OS to base your development on ... three, actually ... You would like me to work with Microsoft products, don't you? > Cheers, > > Hannes
