[U-Boot-Users] RE: start / load addresses for initrd

[Jerry Walden]

>I don't think that was a good idea. Basicly it means that you did not
>understand what's going on,  which  is  not  a  good  base  to  build
>embedded systems on.

Okay - now you got me going... (why is it that every time I have a
communique with you I feel like I talking to a professor is college...)

I discovered that the UART divisor I selected for u-boot is different than
the uart divisor that the function serial_console_setup in
/drivers/char/serial.c.

The kernel I am working with was for the Walnut board, and my board is a
custom
board.  The formula for the uart divisor = serial_input_clock / (16 * 9600).
So my board uses the cpu clock and divides it down to come up with the
serial
input clock, and the Walnut board uses an external clock input.


Jerry Walden

-----Original Message-----
From: u-boot-users-admin at lists.sourceforge.net
[mailto:u-boot-users-admin at lists.sourceforge.net]On Behalf Of Wolfgang
Denk
Sent: Tuesday, March 25, 2003 1:18 PM
To: jwalden at digitalatlantic.com
Cc: U-Boot-Users at Lists. Sourceforge. Net
Subject: Re: [U-Boot-Users] RE: start / load addresses for initrd


In message <EGEGIJHKDKJGAJMGIDPNCEBNCKAA.jwalden at digitalatlantic.com> you
wrote:
>
> Once again - I'm making progress on bringing up Linux
> on a custom 405GPr board using u-boot.

...which is not exactly the topic of this list.

> First - I got my serial console working in Linux.
> I did not have to use TLB's or BAT's to map
> the memory addresses of the UART to properly initialize it.
>
> I simply commented out the initialization that is done in
> /drivers/char/serial.c for the serial console.  The initialization
> that I did in u-boot was sufficient.

I don't think that was a good idea. Basicly it means that you did not
understand what's going on,  which  is  not  a  good  base  to  build
embedded systems on.

> At this point I am trying to get the ramdisk working.  The
> reason I am posting to this list is that I am not sure of the
> command line kernel options for initrd and the ram disk.
...
> Kernel command line: root=/dev/ram console=ttyS0,9600n8 console=tty0

Command line options look ok to me (at least for a  first  test;  you
might want to add "rw" later).

...
> RAMDISK: Compressed image found at block 0
> RAMDISK: incomplete write (ramdisk too small?) (-28 != 32768)
...

Where did you get this ramdisk image from? What makes you think it is
working at all?

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Earth -- mother of the most beautiful women in the universe.
	-- Apollo, "Who Mourns for Adonais?" stardate 3468.1


-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users