| To: | David Kesselring <dkesselr@mmc.atmel.com> |
|---|---|
| Subject: | Re: boot requirements |
| From: | Joe George <joeg@clearcore.com> |
| Date: | Thu, 24 Jul 2003 09:50:31 -0600 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <Pine.GSO.4.44.0307241019450.23101-100000@ares.mmc.atmel.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <Pine.GSO.4.44.0307241019450.23101-100000@ares.mmc.atmel.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630 |
I found Jun's porting howto to be an immense help. http://linux.junsun.net/porting-howto/ I found it easier to port Linux to my board than Yamon. But I guess it probably depends a lot on the kind of port. Joe David Kesselring wrote: I am trying to determine what has to be included in our boot code to start linux. I didn't think I needed to port yamon. What does yamon or pmon provide for starting or debugging(gdb) linux? Does the processor need to be in a specific state or context before jumping from the boot code to the linux downloaded image? If someone can point me to a simple example, I would greatly appreciate it. David Kesselring Atmel MMC dkesselr@mmc.atmel.com 919-462-6587 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | boot requirements, David Kesselring |
|---|---|
| Next by Date: | Re: boot requirements, Wolfgang Denk |
| Previous by Thread: | boot requirements, David Kesselring |
| Next by Thread: | Re: boot requirements, Wolfgang Denk |
| Indexes: | [Date] [Thread] [Top] [All Lists] |