From: Johan Borkhuis <j.borkhuis@dutchspace.nl>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Linuxppc-dev@ozlabs.org
Subject: Re: Patches for ppc?
Date: Fri, 17 Aug 2007 16:43:27 +0200 [thread overview]
Message-ID: <46C5B40F.5040209@dutchspace.nl> (raw)
In-Reply-To: <1187361603.2778.382.camel@shinybook.infradead.org>
David Woodhouse wrote:
> On Fri, 2007-08-17 at 16:36 +0200, Johan Borkhuis wrote:
>
>> Well, this is one of the minor issues I have with the ppc architecture,
>> but I am quite happy with it. Even for this I could make a workaround,
>> but I guess this is something that other might stumble upon.
>>
>> I would like to move to powerpc, but for the moment there is no official
>> support for powerpc, for ppc there is, but I don't have the time to move
>> this to powerpc. So I am afraid I don't have much choice.
>>
>
> It's times like this you suddenly realise you should have paid the extra
> cash for a licence which allows you access to the source code?
>
>
That is not the problem: we have access to all the sources, but I am
waiting for the official support for the powerpc architecure. I am using
an MVME3100 board from Motorola and I know that they are working on it,
but it is not released (yet).
Kind regards,
Johan Borkhuis
next prev parent reply other threads:[~2007-08-17 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 7:43 Patches for ppc? Johan Borkhuis
2007-08-17 8:00 ` Kumar Gala
2007-08-17 12:26 ` David Woodhouse
2007-08-17 14:36 ` Johan Borkhuis
2007-08-17 14:40 ` David Woodhouse
2007-08-17 14:43 ` Johan Borkhuis [this message]
2007-08-17 23:28 ` Satya
2007-08-21 5:25 ` David Gibson
2007-08-21 15:14 ` Segher Boessenkool
2007-08-21 16:11 ` Phil Terry
2007-08-21 16:35 ` Josh Boyer
2007-08-21 16:40 ` Kumar Gala
2007-08-21 17:12 ` Phil Terry
2007-08-21 17:30 ` Scott Wood
2007-08-21 18:09 ` Segher Boessenkool
2007-08-21 17:22 ` Linas Vepstas
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=46C5B40F.5040209@dutchspace.nl \
--to=j.borkhuis@dutchspace.nl \
--cc=Linuxppc-dev@ozlabs.org \
--cc=dwmw2@infradead.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.