From: Victorien Vedrine <victorien.vedrine@ophrys.net>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Logical partition on barebox
Date: Thu, 11 Dec 2014 13:06:18 +0100 [thread overview]
Message-ID: <548988BA.3080700@ophrys.net> (raw)
In-Reply-To: <20141211113246.GH30369@pengutronix.de>
Thanks,
I debug common/partitions/dos.c and the problem is
"dos_extended_partition() is not executed. I found why :
On dos_partition function there is a test to know the type of partition
(line 212). The comment says "partition type 0x05 or 0x0f can be
extended and just 0x0f is tested. The type extended partition on my SD
card is 0x05 and then it doesn't work.
I modify the source code of common/partitions/dos.c with
if ((pentry.dos_partition_type ==
0x0f)||(pentry.dos_partition_type == 0x05)) {
and now it's work.
Victorien
Le 11/12/2014 12:32, Sascha Hauer a écrit :
> On Thu, Dec 11, 2014 at 10:05:10AM +0100, Victorien Vedrine wrote:
>> Thanks for your answer.
>> In a first time, I used a barebox version with the last update at the
>> 10/16/2013. I Found the patch which you are talking about and I update
>> barebox to the version of yesterday and I have the same problem.
>> The partitions of my SD card are this one (with fdisk) :
>>
>> Périphérique Amorçage Début Fin Blocs Id. Système
>> /dev/sdg1 2048 6143 2048 53 OnTrack DM6 Aux3
>> /dev/sdg2 6144 10239 2048 10 OPUS
>> /dev/sdg3 10240 43007 16384 6 FAT16
>> /dev/sdg4 43008 15556607 7756800 5 Étendue
>> /dev/sdg5 43040 567327 262144 83 Linux
>> /dev/sdg6 567360 15556607 7494624 b W95 FAT32
>>
>> I use an iMX28 processor and I have this line on device_init fonction to
>> add the SD card :
>>
>> add_generic_device("mxs_mci", 0, NULL, IMX_SSP0_BASE, 0x2000,
>> IORESOURCE_MEM, &mci_pdata);
> This is correct. If your card is shown then you made everything right
> here.
>
>> Is there any tests that I can do to find a solution or more informations
>> for a bug ?
> You could add a #define DEBUG on top of common/partitions/dos.c (above
> the includes) and see if this gives more information. Otherwise you
> can do some further debugging this file. Does dos_extended_partition()
> get called?
>
> Sascha
>
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-12-11 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 16:21 Victorien Vedrine
2014-12-11 7:04 ` Sascha Hauer
2014-12-11 10:44 ` Victorien Vedrine
[not found] ` <54895E46.5040109@ophrys.net>
2014-12-11 11:32 ` Sascha Hauer
2014-12-11 12:06 ` Victorien Vedrine [this message]
2014-12-15 9:38 ` Sascha Hauer
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=548988BA.3080700@ophrys.net \
--to=victorien.vedrine@ophrys.net \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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