I've never written, or even made sense of a driver before, so I don't know that I'd be helpful. I know no C, nor do I have any line-level coding experience (I've been having fun with Domino Designer though).
Having said that, I'd be happy to make myself useful in whatever way fits what I've mentioned above. Perhaps this is worth discussing privately if I haven't already disqualified myself.
What I was referring to about the kernel seeing hardware was that I run my CW cards through a Magma chassis. I'd be interested in booting SuSE Live on my laptop to see if SuSE's 2.4.xx with 2.6 backported items (specifically useful items being PCMCIA and standardized bus objects) could see the Magma chassis as extra PCI ports, as that's what they are. And if SuSE can see the PCI ports, can it see the CW cards as it would plugged into a native PCI port?
If so, then I'd quite possibly be able to run SuSE Live as a test platform without comprimising my working WinXP setup until I have a workable Linux environment for audio.
Off the top of my head, I really can't think of too many apps beyond Nero and Lotus Notes that I'd really miss. But K3B is getting better by the day, and Lotus is supposed to release a Linux version of Notes in May, so I might have nothing keeping me on the Dark Side of the force.
Perhaps the automation abilities of these Linux sequencers are not very nice, if implemented at all, but as I rarely use VST anything, cept lounge lizard (and even then I'm waiting for CW's electric piano to rise like a phoenix from the rumors), I doubt I'd really miss a lot of the tools available in Cubase as I never really dug into all the features that Cubase SX had to offer. Some of them take as much time to learn and make use of then they are supposed to save.
I had been griping for a long time that there wasn't just a simple (beyond a 909 style on/off) midi sequencer for SFP, as Cubase can sometimes be an impedance when I just want to jam out an idea. Again, I'd have to evaluate how usable these Linux sequencers are, but I can't forsee them being THAT awful that I couldn't work about the same as I do now.
I really would like to have SX 2 in the meantime, but I can't afford the update (I had to get SpaceF's echo first). This sequencer update game can really kiss my ass though. ...SoundForge is no better either.
I can't really see any major difference between version 6 which I own and version 7 which Sony is now sending me a mailer to buy every frickin three days! As if I didn't know what was in their stupid catalogue!

Being free from this kind of BS would be so unbelievably nice... just updating when features I'd use are available... being able to contribute ideas and perhaps, someday add my own code... ahh, bliss indeed in comparison to this corporate nightmare. Then I could save my money for the things that really mattered... like uberPlastic, B2003, Solaris and some RD Modules. ...and of course hassle free recording (yeah right... not in this lifetime).
Anyway, it's hard to tell from this end whether or not Windows is just stupid and needs extra help to operate beyond it's normal hardware resources paradigm, or if Magma's drivers are the necessity of some custom hardware that *nixes cannot see, nor could any other OS.
However, I seem to recall that when I was testing powerbooks with my Magma rig, OS9 didn't really need any drivers for the Magma. It just needed the CW drivers (which again leads us back to your comment) and viewed the Magma PCI ports without so much as a stutter. But Apple may have been prescient enough to have included special Magma drivers as standard issue in OS9, hence my curiousity.
Sam