Your Email Id has won $380,000. in the Western union Promo. send your
Names..
Age..
Sex..
Address..
Tel..
Country..
wunionpaycent...@btinternet.com
Servicio brindado por Velocom - http://www.velocom.com.ar/
___
U-Boot mailing list
U-Boot@lists.denx.d
Subscription request
2010-09-05
liang00fang00yy3
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Hello.
On 04-09-2010 14:34, Albert Aribaud wrote:
> mvsata_ide_initialize_port(): adjust init sequence (SStatus
> should be checked only after all writes to SControl) and
> return success/failure to ide_preinit().
> Also, as some tests showed init durations in the hundreds
> of us, raise the tim
Hello.
On 02-09-2010 19:33, Steve Sakoman wrote:
> This printk was added recently and results in ugly output on systems
> with no NAND:
> NAND: nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x00, Chip
> ID: 0x00 0 MiB
> instead of:
> NAND: 0 MiB
> Signed-off-by: Steve Sakoman
Hi Wolfgang,
I have given boot delay 3 seconds but this delay is for
autobooting , my problem is not able to see u-boot booting messages (
console messages) on Minicom or Kermit as soon as power is up. Its should
take less than 500ms to print console messages when u-boot boot
Hi Sergei,
Le 05/09/2010 12:54, Sergei Shtylyov a écrit :
>> + /* Set control IPM to 3 (no low power) and DET to 1 (initialize) */
>> control = readl(&port->scontrol);
>> control = (control & ~MVSATA_SCONTROL_MASK) | MVSATA_PORT_INIT;
>> + /* Toggle control DET back to 0 (normal operation) */
>
>
Dear Gurumurthy Gowdar,
In message you
wrote:
>
> I have given boot delay 3 seconds but this delay is for
> autobooting , my problem is not able to see u-boot booting messages (
> console messages) on Minicom or Kermit as soon as power is up. Its should
> take less than 500
On 2010/09/04 11:07 AM, Albert ARIBAUD wrote:
> Le 04/09/2010 10:22, Albert ARIBAUD a écrit :
>> Le 26/08/2010 15:16, Rogan Dawes a écrit :
>>
>>> Anything wrong with this patch?
>>
>> I think I finally found what was bugging me with it.
>>
>> Granted, there are cases where we don't want two device
On Sun, Sep 5, 2010 at 3:59 AM, Sergei Shtylyov wrote:
> Hello.
>
> On 02-09-2010 19:33, Steve Sakoman wrote:
>
>> This printk was added recently and results in ugly output on systems
>> with no NAND:
>
>> NAND: nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x00, Chip
>> ID: 0x00 0
Dear Albert ARIBAUD,
In message <4c8201cb.9080...@free.fr> you wrote:
>
> I think that, rather than modifying IDE_BUS(dev), you should introduce a
> CONFIG_SYS_IDE_MAXDEVICE_PER_BUS config option that will limit how many
> devices will be probed for on a given bus.
> Without this config option, f
Hi Wolfgang,
Le 06/09/2010 00:19, Wolfgang Denk a écrit :
> Dear Albert ARIBAUD,
>
> In message<4c8201cb.9080...@free.fr> you wrote:
>>
>> I think that, rather than modifying IDE_BUS(dev), you should introduce a
>> CONFIG_SYS_IDE_MAXDEVICE_PER_BUS config option that will limit how many
>> devices
On 2010/09/06 7:54 AM, Albert ARIBAUD wrote:
> /* OpenRD's two kirkwood busses are SATA: 1 device per bux max) */
> #define CONFIG_SYS_ATA_IDE_CONFIG { \
> { KW_SATA_PORT0_OFFSET, 1}, \
> { KW_SATA_PORT1_OFFSET, 1} \
> }
>
I like this, as it removes assumptions from the code.
FWIW.
Dear Albert ARIBAUD,
In message <4c848200.7080...@free.fr> you wrote:
>
> > First, CONFIG_SYS_IDE_* is for "IDE" (aka "Integrated Drive
> > Electronics"), now usually references as "Parallel ATA", as defined
> > by the underlying AT Attachment (ATA) and AT Attachment Packet
> > Interface (ATAPI) s
Hi again Wolfgang,
Le 06/09/2010 08:05, Wolfgang Denk a écrit :
> Dear Albert ARIBAUD,
>
> In message<4c848200.7080...@free.fr> you wrote:
>>
>>> First, CONFIG_SYS_IDE_* is for "IDE" (aka "Integrated Drive
>>> Electronics"), now usually references as "Parallel ATA", as defined
>>> by the underlyi
14 matches
Mail list logo
