In article <030701003626.M0115412@mirage.ceres.dti.ne.jp>,
Izumi Tsutsui <tsutsui@ceres.dti.ne.jp> wrote:
Newsgroups: netbsd.ports.hp300
Subject: Re: Updated 98265A and MI SCSI driver (Re: 98658 SCSI adaptor and MI SCSI)
Summary: 
Expires: 
References: <030520003601.M0115180@mirage.ceres.dti.ne.jp> <030701003626.M0115412@mirage.ceres.dti.ne.jp>
Sender: 
Followup-To: 
Distribution: netbsd
Organization: 
Keywords: 
Cc: 

In article <030701003626.M0115412@mirage.ceres.dti.ne.jp>,
Izumi Tsutsui <tsutsui@ceres.dti.ne.jp> wrote:
>
>Maybe the left work is to update MD bus_space(9) functions
>to support devices on sparse odd address space to use
>MI mb89352.c for HP 98265 SCSI, but is it OK for now to commit
>a mostly-copied-but-modified MI driver into MD directory?
>Or we should have access method for sparse address (like x68k)?

I think we should have methods for the sparse address space, and
not commit the MI driver in the MD directory.

christos