linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: greenlean <jmgomez@atc.ugr.es>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Linux for ml310
Date: Mon, 14 Jan 2008 10:42:15 -0800 (PST)	[thread overview]
Message-ID: <14808605.post@talk.nabble.com> (raw)
In-Reply-To: <fa686aa40801091410k5d83f124ve009c96683f78ad2@mail.gmail.com>


Hi, I was reading this post and a question came to my mind.

When I try to compile, did I have to copy the EDK driver folder to my Xilinx
2.6 kernel tree and run the cow.tcl script generated by EDK?? Or this is
unnecesay??




Grant Likely-2 wrote:
> 
> On 1/9/08, Joachim Meyer <Jogi95@web.de> wrote:
>> Hi
>>
>> I switched "Xilinx uartlite serieal port support" and "Support for
>> console on Xilinxuartlite serialport" on and "8250/16550 and compatible
>> serial support" off, in the kernel config.
>> Then I removed the things I added in the xparameters.h and compiled
>> successfully.
>> But I have yet a few Questions:
>>
>> - What would you recommend to use? UART-Lite or a 16550 serial port. Can
>> I get a console running on the RS232 Port of the Board with both
>> possibilities?
> 
> if you don't need to change the baud rate at runtime then use the
> uartlite.
> 
> Console works on both.
> 
>>
>> - Can you recommend anything for my next steps to get an running linux
>> (rootfs usw.)? So far I oriented myself on the Klingauf page, but I think
>> it is perhaps not the best one because its too old and some things will
>> probably not work the way he did it anymore.
> 
> Use either ELDK or buildroot.  Personally, I'd like to be using
> OpenEmbedded, but I haven't been successful with that yet.
> 
> Cheers,
> g.
> 
> -- 
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 

-- 
View this message in context: http://www.nabble.com/Linux-for-ml310-tp14675554p14808605.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

  reply	other threads:[~2008-01-14 18:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 20:41 Linux for ml310 Joachim Meyer
2008-01-07 21:02 ` Grant Likely
2008-05-06 17:29   ` Linux for ml410 mojtaba
2008-05-06 17:31     ` Stephen Neuendorffer
2008-01-09 21:29 ` Linux for ml310 Joachim Meyer
2008-01-09 22:10   ` Grant Likely
2008-01-14 18:42     ` greenlean [this message]
2008-01-14 18:47       ` Stephen Neuendorffer
  -- strict thread matches above, loose matches on Subject: below --
2008-01-09 15:19 Joachim Meyer
2008-01-09 15:24 ` Grant Likely
     [not found] <524178230@web.de>
2008-01-09 16:48 ` Grant Likely
2008-01-09 17:29 Joachim Meyer
2008-01-09 18:07 ` Grant Likely
2008-01-09 19:00 Joachim Meyer
2008-01-09 19:16 ` Grant Likely
2008-01-10 10:13 Joachim Meyer
2008-01-10 14:54 ` Grant Likely
2008-01-10 15:44 Joachim Meyer
2008-01-10 15:48 ` Grant Likely
2008-01-11 11:40 Enno Lübbers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14808605.post@talk.nabble.com \
    --to=jmgomez@atc.ugr.es \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).