At 11:22 PM 1/23/00 -0500, "Todd L. Miller" <[EMAIL PROTECTED]> wrote:
>Shared code which uses these drivers should be platform-agnostic, which
>for now means having the same class names.
Common code is identical for all builds. The common code defines the
platform. The jos.platform.keyboard class is an example of common code.
With BCNI, I have eliminated the jos.platform.driver package.
Build-specific code should be different for each build. First, before doing
anything else, a "build" needs to install a build-specific, BCNI-compatible
factory. The jos.host.driver.HostKeyboard is an example of build-specific
code.
The host build should install jos.host.driver.HostFactory. See also the
jos.host.hostinit class as an example.
The i386 build should install the jos.i386.driver.i386Factory. See also the
jos.i386.i386init class as an example.
>At such a point where decaf and the class libraries can support factories
>-- so that common code never sees a 'naked' driver to begin with --
>I'll reconsider my position.
See the BCNI version of the jos.* packages:
<URL:http://www.mindspring.com/~gchii/jos/jjos1e/index.html>
I created a new jos.platform.VGADriver interface. Both jos.host.StandardVGA
and jos.i386.StandardVGA implement the jos.platform.VGADriver interface.
Let me clarify. When I said two different classes should not have the same
name, I meant a fully qualified name such as jos.host.StandardVGA. I find
it most helpful to have both StandardVGA in jos.host and jos.i386.
-----
Bug List
For me, the TestSuite program won't compile at all. There seem to be a few
classes without source code.
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
