From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Hans-Jürgen Lange" <Hans-Juergen.Lange@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.x on IBM thin client 8363
Date: Thu, 5 Jan 2006 19:18:19 -0800 [thread overview]
Message-ID: <20060105191819.594767e0.rdunlap@xenotime.net> (raw)
In-Reply-To: <43BD0E1C.9060705@gmx.de>
On Thu, 05 Jan 2006 13:16:28 +0100 Hans-Jürgen Lange wrote:
> Hello,
>
> I would like to run a 2.6.x kernel on a IBM thin client 8363. There are
> patches available for the 2.4 series of kernels.
> I had a look on these patches and the only thing they do is to expand
> the kernel commandline size to 512 Bytes and a change in
> arch/i386/kernel/head.S that changed the pointer to the commandline to a
> fixed address.
Where are these 2.4 patches that you are referring to?
> In the 2.4.kernel the kernel parameter and command line are ,,moved out
> of the way'' in two steps. And the second step is the one that get patched.
> In the 2.6 kernel this is done in one step. I did get an explanation of
> the startup code for the 2.4. kernel but not for the 2.6. I believe that
> it is no problem to make the changes to get the IBM 8363 running.
>
> I have seen that some people use this machine but all what use the
> newest kernel.
>
> If someone could help me to understand what is going on in the startup
> code or may have a ready to use solution for this problem it would be
> very nice if you could help with get it running.
---
~Randy
next prev parent reply other threads:[~2006-01-06 3:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 12:16 Hans-Jürgen Lange
2006-01-06 3:18 ` Randy.Dunlap [this message]
2006-01-06 9:13 ` Hans-Jürgen Lange
2006-01-06 23:21 ` Randy.Dunlap
2006-01-07 10:10 ` Hans-Jürgen Lange
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=20060105191819.594767e0.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=Hans-Juergen.Lange@gmx.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®