From: acrux <acrux_it@libero.it>
To: Sven Luther <sven.luther@z-innov.com>
Cc: ppc.addon@gmail.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: any chance to use a modern linux kernel on Pegasos1 G3 ?
Date: Wed, 16 Mar 2011 01:23:19 +0100 [thread overview]
Message-ID: <20110316012319.b436ee11.acrux_it@libero.it> (raw)
In-Reply-To: <20110315214149.GA26249@z-innov.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 15 Mar 2011 22:41:49 +0100
Sven Luther <sven.luther@z-innov.com> wrote:
> On Tue, Mar 15, 2011 at 09:08:55PM +0100, Gerhard Pircher wrote:
> >
> > > Well, since this is long dead hardware not produced anymore, i
> > > don't see how the OF could have unbroken itself by moving to
> > > powerpc.
> > >
> > > It has been age since i looked into this, but to the best of my
> > > knowledge (and i wrote the above code or at least the earlier
> > > versions) it should be still broken.
> > Any idea then, how the workaround can be ported to arch/powerpc/ or
> > if there is a better one available?
>
> Sorry, it has been years since i looked these parts of the linux
> kernel, so i don't really know how the arch/powerpc code handles this
> differently. Your best guess is to hunt for the code yourself, and
> find the place. I don't remember though if debugging at that time is
> easily possible though.
>
if chrp support doesn't anymore include Pegasos1 it could be nice to
remove all that dead code. Albeit it's fun that nobody cared about for
it during the ppc=>powerpc switch as Pegasos1 was retired in 2003
and linux-2.6.17 was released in 2006... about three years.
my regards,
Nico
- --
GNU/Linux on Power Architecture
CRUX PPC - http://cruxppc.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
iEYEARECAAYFAk2AAvwACgkQxq34tDeO7LiAMgCfSOueU5IE+CGJQFm56C2vIQdl
WpUAn1MsjAZb/nt1SFtfiB1gLdx79lwX
=LULL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-03-16 0:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 19:05 any chance to use a modern linux kernel on Pegasos1 G3 ? nello martuscielli
2011-03-12 19:38 ` kevin diggs
2011-03-14 12:39 ` nello martuscielli
2011-03-15 16:44 ` nello martuscielli
2011-03-15 16:54 ` Baurzhan Ismagulov
2011-03-15 17:14 ` Gerhard Pircher
2011-03-15 17:49 ` Sven Luther
2011-03-15 20:08 ` Gerhard Pircher
2011-03-15 21:41 ` Sven Luther
2011-03-16 0:23 ` acrux [this message]
2011-03-16 8:14 ` Sven Luther
2011-03-16 23:39 ` nello martuscielli
-- strict thread matches above, loose matches on Subject: below --
2011-03-18 16:11 Gerhard Pircher
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=20110316012319.b436ee11.acrux_it@libero.it \
--to=acrux_it@libero.it \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ppc.addon@gmail.com \
--cc=sven.luther@z-innov.com \
/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).