linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Paubert <paubert@iram.es>
To: Brad Boyer <flar@allandria.com>
Cc: linuxppc-dev@ozlabs.org, debian-kernel@lists.debian.org
Subject: Re: Mac devices on PREP
Date: Sun, 28 Jan 2007 20:23:31 +0100	[thread overview]
Message-ID: <20070128192331.GA17989@iram.es> (raw)
In-Reply-To: <20070127222403.GA24831@cynthia.pants.nu>

On Sat, Jan 27, 2007 at 02:24:03PM -0800, Brad Boyer wrote:
> On Sun, Jan 28, 2007 at 01:01:26PM +0100, Bastian Blank wrote:
> > Currently, the whole bunch of macintosh devices (drivers/macintosh) are
> > listed to be available on all ppc variants. Some of them does not build
> > for prep.
> > 
> > The attached patch restricts the whole bunch to PPC_PMAC. I'm not sure
> > if this is the correct fix.
> 
> I don't know if it still works, but there used to be support for
> ADB on CHRP hardware. I don't have any such hardware to check, so
> someone else will have to comment on that. This is one reason I
> suggested moving ADB out of drivers/macintosh, but at the time
> there was disagreement on that and I never finished the patch I
> was work on anyway.
> 
> Perhaps it should be (PPC_PMAC || PPC_CHRP || MAC) instead as a
> simple fix to prevent it from building on prep.
> 

I don't know what the situation is now, but I'm almost certain that,
once upon a time it was possible to build a kernel that would boot 
on Mac, CHRP and PReP. To be precise, it was the same kernel image
included in different boot wrappers.

	Gabriel

      reply	other threads:[~2007-01-28 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-28 12:01 Mac devices on PREP Bastian Blank
2007-01-27 22:24 ` Brad Boyer
2007-01-28 19:23   ` Gabriel Paubert [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=20070128192331.GA17989@iram.es \
    --to=paubert@iram.es \
    --cc=debian-kernel@lists.debian.org \
    --cc=flar@allandria.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).