Bill Studenmund wrote:

> > The problem is that certain machines work only with the official
> > MRG code. Other machines work only with the ADBTEST code. We don't
> > want to make the ADBTEST code part of the official source until
> > we know it won't make someone's machine (specifically ADB) stop working.
> > I haven't had time to sit down and verify that everything works in
> > ADBTEST that works with MRG.
> 
> One thing I've wondered is why not have merged the code into the kernel, and
> set the two different adb accesses up as compile options? We have two
> different SCSI drivers, why not two different ADB drivers. Thuough it
> sounds like you're close, so the point might be moot.

Actually, this should be able to be done now, I just haven't had the
time to submit the changes. The code needs it's public/private
function declarations split out, and __P defs around some of them. Other
than that it is ready.

	--John