All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Russ <graeme.russ@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Mike Rapoport <mike@compulab.co.il>,
	Alexander Clouter <alex@digriz.org.uk>
Subject: Re: Request For Help - Embedded x86, Kernel 2.6.33 boots, Mounts JFFS2 rootfs, Stops at init
Date: Thu, 29 Apr 2010 23:15:26 +1000	[thread overview]
Message-ID: <4BD9866E.4050101@gmail.com> (raw)
In-Reply-To: <y2zd66caabb1004281614qe5af7fa7i6d9d5ac957ea6520@mail.gmail.com>

Graeme Russ wrote:
> On Thu, Apr 29, 2010 at 1:37 AM, Alexander Clouter <alex@digriz.org.uk> wrote:
>> Graeme Russ <graeme.russ@gmail.com> wrote:
>>> I've been working for a while now getting the x86 U-Boot port up to speed
>>> to boot a linux kernel
>>>
>> ...ewww x86.
> 
>>>
>> What does you /dev directory look like?  You need to have at least the
>> following:
>> ----
>> mknod console c 5 1
>> mknod null c 1 3
>> mknod ttyS0 c 4 64
>> ----
>>
> 
> tick, tick, tick
> 

Success!!!

I feel _really_ stupid about the cause of the problem.... I hadn't set up
the interrupt mapping of the serial ports in my board initialisation
routines in U-Boot. Once I mapped IRQ4 to UART0 it all sprang to life ;)

Big thanks to everyone for helping and a big thanks to all the linux and
GNU developers for creating such a wonderful 'toy' ;)

Graeme

      parent reply	other threads:[~2010-04-30 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 14:08 Request For Help - Embedded x86, Kernel 2.6.33 boots, Mounts JFFS2 rootfs, Stops at init Graeme Russ
2010-04-28 15:32 ` Mike Rapoport
2010-04-28 15:37 ` Alexander Clouter
2010-04-28 23:14   ` Graeme Russ
2010-04-29  8:01     ` Request For Help - Embedded x86, Kernel 2.6.33 boots, Mounts ?JFFS2 " Alexander Clouter
2010-04-29 13:15     ` Graeme Russ [this message]

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=4BD9866E.4050101@gmail.com \
    --to=graeme.russ@gmail.com \
    --cc=alex@digriz.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@compulab.co.il \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.