linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Samuel Chenard" <jsamch@macs.ece.mcgill.ca>
To: Jogi95@web.de
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ml310 kernel2.6 booting problems
Date: Thu, 17 Jan 2008 21:49:13 -0500	[thread overview]
Message-ID: <169c03cb0801171849i59d35893hda44a7f0c5417b58@mail.gmail.com> (raw)

> Date: Thu, 17 Jan 2008 21:19:04 +0100
> From: Joachim Meyer
> Hmmm... I'm not really ready to invest that much time into the PCI for ML=
-310.
> -------------------------------------------------------------------------=
-------
> http://ozlabs.org/pipermail/linuxppc-embedded/2007-December/029211.html
>
> How much work would it be (approximated), and do you think I can success =
(I'm a novice, like you know)?
> Would you help me (Tell me where to start & what to do)?

Hi Joachim,

I was also interested in getting the PCI to run on the ML-310.  I did
spend an evening trying to integrate a patch sent over by Stephen
Neuendorffer from Xilinx.  I managed to get everything to compile
(basically I fixed a few missing macros and had to search a bit to
ensure that the memory mapping was correctly ported).  Unfortunately,
when I tried the new kernel, I think that I must have messed something
up with the interrupt mappings (I am a newbie to PCI) and I had to
remove some interrupt mapping from Stephen's patch.

In any case, my ML-310 was booting the Linux kernel, but something was
not right and I did not get anymore printouts from the UART Lite.
Since I don't have the JTAG cable, I was stuck at this point with
little means to debug the system.  One day I'll spoil myself with one
of those platform JTAG USB cables...

I used Z-modem to transfer files to/from my workstation to my CF card
on the ML-310 and this was an acceptable compromise.

I'd still be interested in having the PCI bus working on the ML-310,
but now that I got my BEE2 booting Linux 2.6, its not such a big
priority for me.  Let me know if you have some success in that
direction.

Regards,

Jean-Samuel
--=20
Integrated Microsystems Laboratory
McGill University, Montr=E9al, QC, CANADA
Web Page: http://chaos.ece.mcgill.ca

             reply	other threads:[~2008-01-18  2:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18  2:49 Jean-Samuel Chenard [this message]
2008-01-19  0:11 ` ml310 kernel2.6 booting problems Ron Sass
2008-01-19  0:35   ` Stephen Neuendorffer
2008-01-19  1:21     ` Ron Sass
2008-01-19  1:23   ` Grant Likely
  -- strict thread matches above, loose matches on Subject: below --
2008-01-17 20:19 Joachim Meyer
2008-01-16 20:02 Joachim Meyer
2008-01-16 20:30 ` Grant Likely
2008-01-16 13:25 Joachim Meyer
2008-01-16 14:50 ` Grant Likely
2008-01-25 13:04   ` greenlean
2008-01-25 15:17     ` Grant Likely

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=169c03cb0801171849i59d35893hda44a7f0c5417b58@mail.gmail.com \
    --to=jsamch@macs.ece.mcgill.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).