From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Joachim Meyer" <Jogi95@web.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux for ml310
Date: Mon, 7 Jan 2008 14:02:21 -0700 [thread overview]
Message-ID: <fa686aa40801071302u78d01f11y5c489553e06c0c01@mail.gmail.com> (raw)
In-Reply-To: <520220685@web.de>
On 1/7/08, Joachim Meyer <Jogi95@web.de> wrote:
> Hi
>
> I'm trying to run a Linux System on a ml310
> I'm using the Kernel 2.4.26 from Bitkeeper und and EDK9.1 Sp2
> I can compile my Kernel without Errors, with a Crosscompiler made by crosstools, if I don't copy the BSP files in the Kernel Directory.
> If I do so, I can't compile. It aborts with the error:
> serial.c:4040: error: 'XPAR_UARTNS550_0_CLOCK_FREQ_HZ' undeclared (first use in this function)
> If I don't use the UART in my Kernel config I get other errors like:
> adapter.c:96: error: `XPAR_XEMAC_NUM_INSTANCES' undeclared (first use in this function)
> I don't really know what to do now. Where should I look for the solution?
Applying the BSP to the 2.4 kernel is a error prone process. You need
to be using the *exact* version of the MontaVista kernel that EDK is
expecting, otherwise it breaks and you need to fix it up manually.
2.6 is much better and you don't need to copy over the whole BSP; just
the xparameters.h file.
> Did I something wrong by generating the BSP or do I have to use an older version of the edk/ise?
>
> When I was trying to find a solution I read some of the things in this mailing list, and now I'm concered about these 2 points
> -Board
> -Kernel Version
> Is it a good idea to use the ml310?
> I want a Linux, an ethernet device, a RS232 device and system-ace. Later I would try to patch the Linux with rtai for real-time-support.
> I read about troubles with the ethernet device on the ml310 because of troubles with the pci bus. Would it be much easier to use an XUP-Board?
> Would it be easier to use the kernel 2.6.x? Has anybody experience in running an rtai-patched Linux on an ml310 - bzw XUP Board?
I strongly recommend moving to 2.6. I don't know if anyone has got
rtai going on it for the virtex, but your chances of getting help are
much higher because virtex 2.6 support is being actively developed.
As for the XUP board, I haven't had a chance to get mine running yet,
but I know others have had good success with it.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2008-01-07 21:02 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 [this message]
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
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=fa686aa40801071302u78d01f11y5c489553e06c0c01@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=Jogi95@web.de \
--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).