From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] LaCie kirkwood boards: allow disk > 2TB
Date: Mon, 10 Jun 2013 16:48:25 +0200 [thread overview]
Message-ID: <20130610164825.2978c579@lilith> (raw)
In-Reply-To: <20130610142926.GW7626@kw.sim.vm.gnt>
Hi Simon,
On Mon, 10 Jun 2013 16:29:26 +0200, Simon Guinot
<simon.guinot@sequanux.org> wrote:
> On Mon, Jun 10, 2013 at 04:20:49PM +0200, Fr?d?ric Leroy wrote:
> >
> > Le 10/06/2013 15:44, Simon Guinot a ?crit :
> > > On Mon, Jun 10, 2013 at 03:30:53PM +0200, Frederic Leroy wrote:
> > > > From: Fr?d?ric Leroy <fredo@starox.org>
> > > >
> > > > For big disk support, we need LBA addressing on 64 bits
> > > > ---
> > > > include/configs/lacie_kw.h | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/include/configs/lacie_kw.h b/include/configs/lacie_kw.h
> > > > index 09b5798..847afcd 100644
> > > > --- a/include/configs/lacie_kw.h
> > > > +++ b/include/configs/lacie_kw.h
> > > > @@ -111,6 +111,7 @@
> > > > #define CONFIG_ENV_SPI_MAX_HZ 20000000 /* 20Mhz */
> > > > #define CONFIG_SYS_IDE_MAXBUS 1
> > > > #define CONFIG_SYS_IDE_MAXDEVICE 1
> > > > +#define CONFIG_SYS_64BIT_LBA /* Allow disk > 2.1TB */
> > >
> > > Hi Frederic,
> > >
> > > I see a comment at disk/part_efi.c:25. It claims that maximum size of
> > > addressable storage is limited to 2TB even with CONFIG_SYS_64BIT_LBA
> > > enabled. Is that not true anymore ?
> > I didn't see this comment.
> > With my patch, the "ide reset" command recognize nicely a 3TB harddrive.
> > Else, it reports the size % 2TB and then u-boot reports error in the GPT.
> >
> > I can read the GPT and boot from a loaded file from the first partition.
> > However, an "ext2ls" on a partition at the end of the disk outputs garbage.
> >
> > At least, the patch allow to use the first 2 TB for booting.
>
> Acked-by: Simon Guinot <simon.guinot@sequanux.org>
>
> I add Prafulla to the Cc recipient. He is the one who will pick your
> patch eventually.
Not necessarily, as this is only a target configuration change, not a
SoC change -- actually, nothing in the patch is related to Marvell SoCs.
This patch could go directly in mainline even, but usually I do the
picking up if it's an ARM target.
> Regards,
>
> Simon
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-06-10 14:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 13:30 [U-Boot] [PATCH] LaCie kirkwood boards: allow disk > 2TB Frederic Leroy
2013-06-10 13:44 ` Simon Guinot
2013-06-10 14:20 ` Frédéric Leroy
2013-06-10 14:29 ` Simon Guinot
2013-06-10 14:48 ` Albert ARIBAUD [this message]
2013-06-13 11:33 ` Albert ARIBAUD
2013-06-13 13:03 ` Frédéric Leroy
2013-06-13 13:21 ` Albert ARIBAUD
2013-06-13 13:36 ` Frédéric Leroy
2013-06-13 20:32 ` Sascha Silbe
2013-06-14 11:07 ` [U-Boot] [PATCH] Fix block device accesses beyond 2TiB Sascha Silbe
2013-06-17 20:26 ` Marek Vasut
2013-06-22 10:07 ` Albert ARIBAUD
[not found] ` <51C598A6.8040406@starox.org>
2013-06-22 15:31 ` Albert ARIBAUD
2013-06-24 9:46 ` Frédéric Leroy
2013-06-24 21:13 ` Sascha Silbe
2013-06-24 21:26 ` [U-Boot] [PATCH] Fix ext2/ext4 filesystem " Frederic Leroy
2013-06-24 22:26 ` Sascha Silbe
2013-06-25 6:10 ` Frederic Leroy
2013-06-25 20:42 ` Sascha Silbe
2013-06-26 16:11 ` [U-Boot] [PATCH v2] " Frédéric Leroy
2013-07-11 10:41 ` Albert ARIBAUD
2013-07-16 14:37 ` [U-Boot] [U-Boot, " Tom Rini
2013-06-26 20:25 ` [U-Boot] Fix block device " Tom Rini
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=20130610164825.2978c579@lilith \
--to=albert.u.boot@aribaud.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox