linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Glines <mark@glines.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: kurobox kernel
Date: Tue, 26 Dec 2006 12:14:12 -0800	[thread overview]
Message-ID: <45918294.3080303@glines.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0612260019430.3424@poirot.grange>

Guennadi Liakhovetski wrote:
> On Mon, 25 Dec 2006, Mark Glines wrote:
> 
>> Guennadi Liakhovetski wrote:
>>
>> Yes, I do very much intend to test it on real hardware.  I have a couple of
>> Kurobox HGs which desperately need a 21st century kernel.  I still need to
> 
> Ah, what a pity:-) I mean, it is good, but it's exactly the same hardware 
> I developed this port for and tested on. So, it should be easy. If you 
> have any problems with your setup, look in linkstation / kurobox mailing 
> list archives, I posted some instructions there for setting up a suitable 
> u-boot version. Or just ask me. Or I could even just send you binaries to 
> start with. Do you have JTag?...

No, I haven't made any hardware mods yet.

Thanks for the offer.  Kernel binaries might actually help, just to make 
sure the hardware and bootloader are working properly.

The instructions on 
http://www.linuxnotincluded.pwp.blueyonder.co.uk/linkstation/u-bootinstall.html 
were a little broken in a few places, but still very helpful.  I've got 
U-boot 1.1.4 up and running.  It's just booting the old 2.4.17_mvl21 
from flash right now... 2.6.20-rc2 fails to boot.

I have ordered some serial port voltage converters, which I hope to use 
to get some diagnostics from the 2.6.20-rc2 kernel.  I don't hear any 
disk activity, and I wasn't able to get netconsole working, so I think 
it is dying fairly early in the boot process.  (At least, before PCI and 
network are up.)

Mark

  reply	other threads:[~2006-12-26 20:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.ne7N9dqjDz5qS4D/fowPKdPc4ZY@ifi.uio.no>
     [not found] ` <fa.pM17YEcICUlveSt/vbSKGv6sFWk@ifi.uio.no>
2006-12-25 19:45   ` Linux 2.6.20-rc2: forgot how to make a zImage on powerpc? Mark Glines
2006-12-25 20:31     ` Guennadi Liakhovetski
2006-12-25 21:47       ` [PATCH] powerpc: linkstation uses uimage style zImages Mark Glines
2006-12-25 22:54         ` Guennadi Liakhovetski
2006-12-25 23:07           ` Mark Glines
2006-12-25 23:23             ` Guennadi Liakhovetski
2006-12-26 20:14               ` Mark Glines [this message]
2006-12-26 21:23                 ` kurobox kernel Guennadi Liakhovetski
2006-12-28 20:53                   ` Mark Glines
2006-12-28 21:02                     ` Scott Wood
2006-12-28 21:07                       ` Xianghua Xiao
2006-12-28 21:11                     ` Guennadi Liakhovetski
2006-12-28 23:28                       ` Mark Glines
2006-12-29  0:31                         ` Guennadi Liakhovetski
2006-12-29  2:52                           ` Mark Glines
2006-12-29 17:58                           ` Mark Glines
2006-12-29 18:35                             ` Guennadi Liakhovetski

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=45918294.3080303@glines.org \
    --to=mark@glines.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linuxppc-dev@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).