On Tue, May 27, 2008 at 03:47:56PM -0700, vb wrote:
> On Tue, May 27, 2008 at 3:36 PM, Adrian Bunk <bunk@xxxxxxxxxx> wrote:
> > On Tue, May 27, 2008 at 11:08:53AM -0700, vb wrote:
> >> >On Thu, May 22, 2008 at 10:52 AM, David Woodhouse <dwmw2@xxxxxxxxxxxxx> wrote:
> >> > On Thu, 2008-05-22 at 10:24 -0700, vb wrote:
> >> >> Do I have to describe the CF card in the dreaded DTS file (I don't see
> >> >> any reference to IDE in the prom*.c and friends though).
> >> >
> >> > Yes, you do. Use libata instead of the old IDE driver, and see
> >> > pata_of_platform.
> >>
> >> David, again thank you for this insight. I got to spend some more time
> >> on this and (unfortunately!) have some more questions:
> >>
> >> SCSI support gets added as soon as CONFIG_ATA gets enabled in
> >> drivers/ata/Kconfig - is this intentional/necessary? My embedded
> >> target sure doesn't have any SCSI hardware, all it needs is a CF card
> >> support in true IDE mode.
> >>
> >> These are config flags added 'automagically' as soon as ATA is enabled
> >> does it make sense?
> >>
> >> CONFIG_SCSI=y
> >> CONFIG_SCSI_DMA=y
> >> CONFIG_SCSI_LOWLEVEL=y
> >> CONFIG_SCSI_PROC_FS=y
> >> CONFIG_SCSI_WAIT_SCAN=m
> >>...
> >
> > CONFIG_SCSI_LOWLEVEL can be disabled (but it doesn't make any difference
> > for the code).
> >
> > CONFIG_SCSI_PROC_FS can be disabled, which will save you a few bytes.
>
> I am not really worried about saving memory, I just am trying to
> understand the reason the SCSI driver is included in the first place -
> SCSI is a much heavier protocol than what is needed here - isn't it?
>...
ATAPI uses the SCSI command set, so using parts of the SCSI layer for
implementing ATA support is not unreasonable.
> cheers,
> Vadim
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
To unsubscribe from this list: send the line "unsubscribe linux-embedded" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
