Re: [U-Boot] [PATCH 1/3] OMAP3/4/5/AM33xx: Correct logic for checking FAT or RAW MMC

2013-04-09 Thread Tom Rini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/09/2013 10:52 AM, Peter Korsgaard wrote: >> "Tom" == Tom Rini writes: > > Tom> In the case of booting from certain peripherals, such as UART, > we must Tom> not see what the device descriptor says for RAW or FAT > mode because in Tom> addit

Re: [U-Boot] [PATCH 1/3] OMAP3/4/5/AM33xx: Correct logic for checking FAT or RAW MMC

2013-04-09 Thread Peter Korsgaard
> "Tom" == Tom Rini writes: Tom> In the case of booting from certain peripherals, such as UART, we must Tom> not see what the device descriptor says for RAW or FAT mode because in Tom> addition to being nonsensical, it leads to a hang. This is why we have Tom> a test currently for the bo

Re: [U-Boot] [PATCH 1/3] OMAP3/4/5/AM33xx: Correct logic for checking FAT or RAW MMC

2013-04-08 Thread Sricharan R
Hi Tom, On Friday 05 April 2013 09:51 PM, Tom Rini wrote: > In the case of booting from certain peripherals, such as UART, we must > not see what the device descriptor says for RAW or FAT mode because in > addition to being nonsensical, it leads to a hang. This is why we have > a test currently f

[U-Boot] [PATCH 1/3] OMAP3/4/5/AM33xx: Correct logic for checking FAT or RAW MMC

2013-04-05 Thread Tom Rini
In the case of booting from certain peripherals, such as UART, we must not see what the device descriptor says for RAW or FAT mode because in addition to being nonsensical, it leads to a hang. This is why we have a test currently for the boot mode being within range. The problem however is that o