From: Greg Ungerer <gregungerer@westnet.com.au>
To: Angelo Dureghello <angelo@sysam.it>, linux-m68k@vger.kernel.org
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: my contribution
Date: Wed, 10 Feb 2016 21:51:59 +1000 [thread overview]
Message-ID: <56BB245F.8080601@westnet.com.au> (raw)
In-Reply-To: <56BB0826.5040602@sysam.it>
Hi Angelo,
On 10/02/16 19:51, Angelo Dureghello wrote:
> Hi John Paul,
>
> thanks,
>
> well as Geert says, mcf5307 is no-mmu, i am developing some mcf54416
> stuff now, so maybe in the near future i could contribute to Debian
> too.
You could send patches for the linux kernel to support the
mcf54416. We have base support for v4e with and without MMU.
So patches to extend that to support the mcf54416 would be
great.
Regards
Greg
> On 09/02/2016 23:40, John Paul Adrian Glaubitz wrote:
>> Hi Angelo!
>>
>> On 02/09/2016 11:14 PM, Angelo Dureghello wrote:
>>> Let me know if there is some job to do, where i can be useful.
>>
>> Join debian-68k@lists.debian.org:
>>
>>> https://lists.debian.org/debian-68k/
>>
>> And help fixing packages that don't build on m68k.
>>
>> Here are some hints on how to get a working m68k Debian:
>>
>>> https://wiki.debian.org/M68k
>>> https://wiki.debian.org/M68k/Installing
>>> https://wiki.debian.org/Aranym/Quick
>>
>> Adrian
>>
>
> Regards,
> Angelo Dureghello
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-02-10 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 22:14 my contribution Angelo Dureghello
2016-02-09 22:40 ` John Paul Adrian Glaubitz
2016-02-10 9:29 ` Geert Uytterhoeven
2016-02-10 9:34 ` Philippe De Muyter
2016-02-10 9:50 ` John Paul Adrian Glaubitz
2016-02-10 11:04 ` Angelo Dureghello
2016-02-10 9:51 ` Angelo Dureghello
2016-02-10 11:51 ` Greg Ungerer [this message]
2016-02-10 12:00 ` Angelo Dureghello
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=56BB245F.8080601@westnet.com.au \
--to=gregungerer@westnet.com.au \
--cc=angelo@sysam.it \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@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