public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin Brulisauer" <martin@uceb.org>
To: George France <france@handhelds.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild 2.5.26 - arch/alpha
Date: Tue, 23 Jul 2002 19:01:07 +0200	[thread overview]
Message-ID: <3D3DA7F3.9275.1480075C@localhost> (raw)
In-Reply-To: <02072311055101.22920@shadowfax.middleearth>

On 23 Jul 2002, at 11:05, George France wrote:
> that version for a while until it is stable.  In the past few months most of 
> the efforts have been spent on 2.4.9.  Currently there have been discussions 
> in regard to:
> 
> 1) porting all those patches for 2.4.9 forward to 2.4.[18-19] and 2.5.x.  

I am currently running 2.4.18 from SuSE without any (major) 
problems. I found it here:
ftp://ftp.suse.com/pub/people/sf/axp/7.1/RPMS/kernel-source-
2.4.18.SuSE-0.alpha.rpm.
Then I took arch/alpha/kernel/core_cia.c from version 2.4.12
(the current version does not run on XLT's booting with MILO;
the latest one is 2.4.12).

> 2) taking a look at the latest 2.5.x in the next few weeks, as we are aware 
> that 2.5.x does not compile on Alpha.

Hopefully I can fix core_cia.c to run on XLT's (it's hard to find any 
documentation on this toppic) and arch/alpha/kernel/setup.c for 
machines booting with linload.exe/MILO because the hwrpb
struct is built by MILO and does not match the one booting from
SRM (eg. empty percpu struct resulting in a cpucount of zero
in /proc/cpuinfo).

Regards,
Martin


  parent reply	other threads:[~2002-07-23 16:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-21 13:54 kbuild 2.5.26 - arch/alpha Martin Brulisauer
     [not found] ` <001101c230d7$c5973c40$1211a8c0@pitzeier.priv.at>
2002-07-23 12:42   ` Martin Brulisauer
2002-07-23 13:28     ` Jan-Benedict Glaw
2002-07-23 23:34       ` Oliver Pitzeier
2002-07-24  6:53         ` Thunder from the hill
2002-07-24  7:07           ` Thunder from the hill
2002-07-24  7:13           ` Martin Brulisauer
2002-07-24  7:45             ` Thunder from the hill
2002-07-26  9:47       ` [alpha 2.5.28] " Ivan Kokshaysky
2002-07-23 15:05     ` George France
2002-07-23 16:24       ` Ghozlane Toumi
2002-07-23 17:01       ` Martin Brulisauer [this message]
2002-07-23 19:00         ` George France
2002-07-23 19:08           ` Sven Koch
2002-07-23 21:24             ` Jay Estabrook
2002-07-23 20:18           ` Jay Estabrook
2002-07-23 23:44           ` Oliver Pitzeier
2002-07-23 23:35     ` Oliver Pitzeier
2002-07-23 23:54 ` Oliver Pitzeier
2002-07-24  3:51   ` Thunder from the hill
     [not found] <002b01c23279$84be70a0$1211a8c0@pitzeier.priv.at>
     [not found] ` <02072318292300.02533@shadowfax.middleearth>
2002-08-09 10:00   ` Martin Brulisauer
2002-08-09 14:23     ` George France
2002-08-09 17:51     ` Måns Rullgård
2002-08-09 21:03     ` Thunder from the hill
     [not found] <20020723202538.NYJJ13064.tomts23-srv.bellnexxia.net@there>
     [not found] ` <001701c2329b$a812f6d0$1211a8c0@pitzeier.priv.at>
2002-07-23 23:26   ` Martin Brulisauer
     [not found] <3D3DF93C.16904.30BF311@localhost>
     [not found] ` <001a01c2329d$6d588fd0$1211a8c0@pitzeier.priv.at>
2002-07-23 23:21   ` Martin Brulisauer
  -- strict thread matches above, loose matches on Subject: below --
2002-07-20  8:41 Martin Brulisauer

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=3D3DA7F3.9275.1480075C@localhost \
    --to=martin@uceb.org \
    --cc=france@handhelds.org \
    --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