ferent ECC modes for different parts of the flash is unfortunate, but
sometimes mandated by circumstance. The NAND subsystem isn't really set
up to handle this, though changing it temporally is a hackish substitute.
Ok, thanks for clarifying.
--
Orjan Friberg
FlatFrog
. software
implementations, whether block 0 has different ECC requirement etc)?
--
Orjan Friberg
FlatFrog Laboratories AB
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
seems to have been fixed in the
u-boot-nand-flash repo.)
Thanks,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
gt; was a local hack. (I couldn't find it in the ml archives.)
>
> This has never been supported in mainline code.
Ok, thanks. I'm going to give it a shot and see if I can come up with
something sensible.
--
Orjan Friberg
FlatFrog Laboratories AB
construct doesn't work with 2011.03. I'm trying to find out
how this was implemented, and if it was ever part of mainline or if it
was a local hack. (I couldn't find it in the ml archives.)
Thanks,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
_
On 2011-08-08 21:37, Remy Bohmer wrote:
> Whoops... Not applied to u-boot-usb, since the timeout code is broken.
> It should wait for a certain time, not a certain count.
Agreed, patch withdrawn.
--
Orjan Friberg
FlatFrog Laboratories AB
___
On 2011-07-07 14:27, Orjan Friberg wrote:
> On 2011-07-07 11:37, Orjan Friberg wrote:
>> It seems the boot rom must be doing some initialization of the USB phy
>> (this is with a TPS65920).
>
> I forgot to add that I'm using a configuration header and not x-loader
>
On 2011-07-07 11:37, Orjan Friberg wrote:
> It seems the boot rom must be doing some initialization of the USB phy
> (this is with a TPS65920).
I forgot to add that I'm using a configuration header and not x-loader
as the 1st stage bootloader.
On a BeagleBoard xM (with x-loader)
ot rom must be doing some initialization of the USB phy
(this is with a TPS65920). Dumping the I2C regs of the USB phy in
u-boot shows a lot of differences between the two boot modes.
This is on a custom board, BeagleBoard derived but with a 3730.
Any ideas?
Thanks,
Orjan
--
Orjan Friberg
L.D5 = 0" so that PHY doesn't drive 5V.
> 2. Do not set musb_cfg.extvbus
Great, thanks for clarifying (and agreed on all points).
It seems the best I can do is turn off DRVVBUS as soon as the chip has
entered host mode (and turned thus it on).
Thanks,
Orjan
, we have added an external vbus supply to be able
to draw > 100 mA.)
Thanks,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
0.06) and the git repo
for u-boot-ti and they all have the same construct.
Thanks,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Use pre-decrement to leave timeout at 0 when the timeout happens (which is what
the timeout detecting code expects).
Signed-off-by: Orjan Friberg
---
drivers/usb/musb/musb_hcd.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/musb/musb_hcd.c b/drivers/usb
if (readb(&musbr->devctl) & MUSB_DEVCTL_HM)
break;
--
Orjan Friberg
FlatFrog Laboratories AB
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
ems to have the same construct.)
Thanks,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
for the BeagleBoard; I'm trying to get dmareq2
working on a custom 3730 board.)
Thanks,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
16 matches
Mail list logo
