From: David Miller <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: Sparc32 not working:2.6.23-rc1 (git commit
Date: Sun, 29 Jul 2007 05:40:37 +0000 [thread overview]
Message-ID: <20070728.224037.39158363.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0707281903350.27869@mtfhpc.demon.co.uk>
From: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Date: Sat, 28 Jul 2007 19:18:50 +0100 (BST)
> Do you have any Sparc32/generic Sparc patches that have not already been
> pushded up to
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
No.
> I have just tried out the latest commit on my sun4c SS1 and have found it
> to have a NULL pointer bug. I can't give any details as the serial console
> support is broaken and on the cgthree console, the information scrolled of
> the top of the console before I had a chance to read any of the key
> details.
>
> In addition, enabling CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY killed the
> kernel while starting up the cgthree (it just stopped - no messages).
>
> Looks like I am going to have to step through the changes from my
> working v2.6.22 kernel slowly.
Yes, basically expect sparc32 to break as long as there is not
a maintainer that constantly pulls from upstream and tests things
on a frequent basis as I do for sparc64.
Feel free to step up and be "the one" :-)
next prev parent reply other threads:[~2007-07-29 5:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 18:18 Sparc32 not working:2.6.23-rc1 (git commit 1e4dcd22efa7d24f637ab2ea3a77dd65774eb005) Mark Fortescue
2007-07-28 21:48 ` Sparc32 not working:2.6.23-rc1 (git commit Krzysztof Helt
2007-07-28 22:38 ` Krzysztof Helt
2007-07-28 23:21 ` Mark Fortescue
2007-07-29 5:40 ` David Miller [this message]
2007-07-29 8:29 ` Mark Fortescue
2007-07-29 9:05 ` David Miller
2007-07-29 9:57 ` Mark Fortescue
2007-07-29 14:44 ` Mark Fortescue
2007-07-29 14:44 ` Sparc32 not working:2.6.23-rc1 (git commit 1e4dcd22efa7d24f637ab2ea3a77dd65774eb005) Mark Fortescue
2007-07-29 15:45 ` Sparc32 not working:2.6.23-rc1 (git commit Krzysztof Helt
2007-07-29 18:26 ` Mark Fortescue
2007-07-29 18:26 ` Sparc32 not working:2.6.23-rc1 (git commit 1e4dcd22efa7d24f637ab2ea3a77dd65774eb005) Mark Fortescue
2007-07-29 18:26 ` Mark Fortescue
2007-07-29 20:56 ` Sparc32 not working:2.6.23-rc1 (git commit Adrian Bunk
2007-07-29 20:56 ` Sparc32 not working:2.6.23-rc1 (git commit 1e4dcd22efa7d24f637ab2ea3a77dd65774eb005) Adrian Bunk
2007-07-29 20:56 ` Adrian Bunk
2007-07-29 22:01 ` Sparc32 not working:2.6.23-rc1 (git commit Mark Fortescue
2007-07-29 22:01 ` Sparc32 not working:2.6.23-rc1 (git commit 1e4dcd22efa7d24f637ab2ea3a77dd65774eb005) Mark Fortescue
2007-07-29 22:01 ` Mark Fortescue
2007-07-29 20:56 ` Sparc32 not working:2.6.23-rc1 (git commit Krzysztof Helt
2007-07-29 21:54 ` Mark Fortescue
2007-07-30 14:19 ` Mark Fortescue
2007-07-30 18:16 ` Krzysztof Helt
2007-07-31 1:22 ` David Miller
2007-07-31 3:05 ` Mark Fortescue
2007-07-31 16:57 ` Krzysztof Helt
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=20070728.224037.39158363.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@vger.kernel.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 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.