From: Jon Masters <jonmasters@gmail.com>
To: Luca Giuliani <l.giuliani@tiscali.it>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: Linux on Memec Virtex II Pro V4P7 Rev. 3
Date: Tue, 5 Oct 2004 16:15:33 +0100 [thread overview]
Message-ID: <35fb2e5904100508157a393ee2@mail.gmail.com> (raw)
In-Reply-To: <000001c4aace$245a5060$6500a8c0@PortatileLG>
[ Will followup only to linuxppc-embedded ]
On Tue, 5 Oct 2004 13:26:15 +0200, Luca Giuliani <l.giuliani@tiscali.it> wrote:
> I'm a newbie of Linux on embedded devices and I tried longly to make
> Linux work on the embedded PPC405 on the Memec Virtex II Prov V4P7 board
I have one of these boards which we base our platform upon.
> WITHOUT P160 module.
I use an SMC91111 on a custom ISA bodge - no P160 here but we do also
use xuart et al. (Why would you want to buy the Xilinx Ethernet MAC or
use the P160 anyway - who needs a second serial port :P).
> I'm using the patched 2.4.22 patched by Mind.be, freely available on
> their FTP site.
You need a few extra patches such as the one to use even TLBs only
that I and others ended up implementing on the engineering v2ps. I'll
stick up my mods at some point (product not shipping at this moment so
this'll be done at some point before then).
> The boot process always freezes after the "Uncompressing Linux...done"
There's a bunch of problems with that board. You end up disabling the
ME reporting on those boards by bodging the MSR as you mentioned.
That's a bastard to figure out.
> The only way to make the kernel INITIATE the boot process was to modify
> the MSR mask (/include/asm-ppc/processor.h) as to disable the Machine
> Check, but this is not a good idea!
It's necessary elsewhere too so I wouldn't get too worked up about
that. The Monta guys don't get this problem on their shiney ML300s but
then if I wanted to expense 6K to Xilinx for a touchscreen board I
might buy one too :-).
> The first thing that came to my mind was that there was an error in the
> hardware design, but it was auto-generated with the "Base platform
> builder" wizard included in EDK 6.2 and then customized only to meet the
> requirements of the Mind kernel.
The EDK stuff sucks horribly - avoid the autogenerated platforms
beyond the necessary. Certainly don't use the xparms file from EDK in
your design, that supports the notion Xilinx have of shoving a HAL in
to the kernel.
> Has someone succeeded in booting Linux on this device WITHOUT P160
> expansion card?
Yes. Spam me.
> If so I kindly ask you to answer me privately, at least to know how you
> built the hardware design, which kernel did you use and which are the
> vital parameters to be set in the kernel.
A custom 2.4.23 based purely on the stock kernel from kernel.org. I
use a few Mind patches, some stuff from the Monta tree and a bunch of
hacks I did myself. It boots using my own firmware which is in the
hardware image on the SystemACE and runs with a root RAMdisk off the
sysace (but you need to use my nointr sysace patch for this board).
I can help you with generalities but for various commerical reasons
there's a limit to how much I can talk about here or in private mail
concerning our specific design.
Cheers,
Jon.
next prev parent reply other threads:[~2004-10-05 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 11:26 Linux on Memec Virtex II Pro V4P7 Rev. 3 Luca Giuliani
2004-10-05 14:12 ` Matt Porter
2004-10-05 15:15 ` Jon Masters [this message]
2004-10-05 16:05 ` Andrei Konovalov
2004-10-05 22:07 ` Jon Masters
2004-10-06 15:41 ` Andrei Konovalov
2004-10-07 1:03 ` Jon Masters
2004-10-07 22:34 ` Tony Lee
2004-10-08 0:12 ` Jon Masters
2004-10-08 2:53 ` Tony Lee
2004-10-09 19:27 ` Jon Masters
2004-10-10 4:26 ` Tony Lee
2004-10-10 22:20 ` Jon Masters
-- strict thread matches above, loose matches on Subject: below --
2004-10-05 16:34 [MailServer Resend]Resending quarantined email -- use caution when opening.Re: " Administrator
2004-10-05 17:00 ` Ralph Siemsen
2005-03-24 19:01 Nguyen, Tony (US SSA)
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=35fb2e5904100508157a393ee2@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=l.giuliani@tiscali.it \
--cc=linuxppc-dev@ozlabs.org \
--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).