summaryrefslogtreecommitdiffstats
path: root/examples
diff options
context:
space:
mode:
authorEgbert Eich <eich@suse.com>2013-04-09 05:46:14 +0000
committerTom Rini <trini@ti.com>2013-05-01 16:24:01 -0400
commit9d956e0fefa39ba49250f61e3c7aa3dadafdb7fd (patch)
treeb8c238604b78488bb74da32112bfd8369e15e8f9 /examples
parent8bfa195e4e7ecbbabd4f070a3640212a5ac4ebde (diff)
downloadtalos-obmc-uboot-9d956e0fefa39ba49250f61e3c7aa3dadafdb7fd.tar.gz
talos-obmc-uboot-9d956e0fefa39ba49250f61e3c7aa3dadafdb7fd.zip
disk/part_dos: check harder for partition table
Devices that used to have a whole disk FAT filesystem but got then partitioned will most likely still have a FAT or FAT32 signature in the first sector as this sector does not get overwritten by a partitioning tool (otherwise the tool would risk to kill the mbr). The current partition search algorithm will erronously detects such a device as a raw FAT device. Instead of looking for the FAT or FAT32 signatures immediately we use the same algorithm as used by the Linux kernel and first check for a valid boot indicator flag on each of the 4 partitions. If the value of this flag is invalid for the first entry we then do the raw partition check. If the flag for any higher partition is wrong we assume the device is neiter a MBR nor PBR device. Signed-off-by: Egbert Eich <eich@suse.com>
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud