All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PATCH : ppp + big-endian = kernel crash
Date: Tue, 31 May 2005 00:05:51 +1000	[thread overview]
Message-ID: <429B1DBF.1060205@snapgear.com> (raw)

Andi Kleen <ak () muc ! de> writes:
> Andrew Morton <akpm@osdl.org> writes:
>>> 
>>> So many variants of tunneling and protocol encapsulation can result in
>>> unaligned packet headers, and as a result platforms really must
>>> provide proper unaligned memory access handling in kernel mode in
>>> order to use the networking fully.
>>
>> As Philippe mentioned, old 68k's simply cannot do this.
> 
> An 68000 cannot, but 68010+ can. Are there really that many 68000 users
> left? 

Probably not of the 68000 as such, but the "new" generation of
68000 parts, Motorola/Freescales ColdFire family. There is quite
a few of them, used in all sorts of embedded applications.
And they are still churning out new varients of it. The majority
of them are MMUless - but not all.

Regards
Greg


             reply	other threads:[~2005-05-30 14:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 14:05 Greg Ungerer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-29 19:48 PATCH : ppp + big-endian = kernel crash Philippe De Muyter
2005-05-29 20:52 ` David S. Miller
2005-05-29 21:38   ` Philippe De Muyter
2005-05-29 21:55     ` David S. Miller
2005-05-30  2:52       ` Andrew Morton
2005-05-30  3:11         ` David S. Miller
2005-06-01 15:26           ` Philippe De Muyter
2005-05-30 10:22         ` Andi Kleen
2005-05-30 13:01           ` cutaway
2005-05-30  7:16   ` Giuliano Pochini

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=429B1DBF.1060205@snapgear.com \
    --to=gerg@snapgear.com \
    --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 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.