From: Tor Krill <tor@excito.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Merge code duplication in ata.h and libata.h
Date: Mon, 31 Mar 2008 09:10:43 +0000 (UTC) [thread overview]
Message-ID: <0JEB3vTG.1206954643.2020790.tor@localhost> (raw)
In-Reply-To: <1206949069.3662.8.camel@localhost.localdomain>
On 3/31/2008, "Dave Liu" <r63238@freescale.com> wrote:
>> >Don't do this.
>> >
>> >I don't think the ATA_SECT_BYTESIZE is better than
>> >the ATA_SECT_SIZE.
>>
>> The big problem here is that ata.h defines ATA_SECT_SIZE as 256 Words
>> where libata defines it as 512 Bytes.
>>
>> I did not want to change the old define since it would possibly break
>> more than the fsl driver.
>
>When I grep 'ATA_SECT_SIZE', I can *not* find any files including the
>ATA_SECT_SIZE before the fsl_sata.c.
Well, the ata_piix driver for one uses it, but only includes ata.h. But
that is the only one in the tree right now.
>> But the problem still remains, it is currently impossible to use both
>> libata.h and ata.h.
>
>Why need use both them?
>I believe the libata.h is enough.
Since my driver for the sil3114 uses "legacy mode" it uses a lot of the
ata commands directly in PIO mode. These are defined in ata.h (Both in
u-boot and Linux)
>If the libata.h is not enough for you, I suggest you update it from the
>latest linux kernel.
Still, the kernel has both a ata.h and a libata.h, where libata.h
includes ata.h. And where ATA_SECT_SIZE, and the other defines i use,
actually is defined in ata.h albeit as 512 bytes :).
>I think it is correct way to handle it.
>It will be more easy to to maintain the header.
I have no problem with either solution. If its ok to add the defines to
libata.h instead i will do that?
/Tor
next prev parent reply other threads:[~2008-03-31 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 6:35 [U-Boot-Users] [PATCH] Merge code duplication in ata.h and libata.h Tor Krill
2008-03-31 6:45 ` Dave Liu
2008-03-31 8:20 ` Tor Krill
2008-03-31 7:37 ` Dave Liu
2008-03-31 9:10 ` Tor Krill [this message]
2008-03-31 8:40 ` Dave Liu
2008-03-31 10:45 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0JEB3vTG.1206954643.2020790.tor@localhost \
--to=tor@excito.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.