All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: adaplas@gmail.com, benh@kernel.crashing.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Anton Vorontsov <avorontsov@ru.mvista.com>
Subject: Re: [PATCH 1/2] fb: add support for foreign endianness
Date: Wed, 20 Feb 2008 16:43:42 +0100	[thread overview]
Message-ID: <47BC4AAE.8020908@anagramm.de> (raw)
In-Reply-To: <18363.31427.989835.105966@cargo.ozlabs.ibm.com>

Paul Mackerras schrieb:
> Andrew Morton writes:
> 
>> Bizarrely, the original author of the patch (Anton) has fallen off the cc. 
>> Could whoever did that please thwap himself?
>>
>> Anyway, my head is now officially spinning.  Did anyone actually have a
>> reason why we shouldn't proceed with Anton's patch?
> 
> I was wondering if it would be sufficient to provide alternative
> versions of fb_readl, fb_writel etc. that do byte-swapping.  That
> would mean that all framebuffers would have to have the same
> endianness, but that would suffice for embedded systems such as
> Anton's and would end up a lot simpler IMHO.

Yes. At least the affected PowerPC platforms can do byte-swapping on
the fly, so this should be sufficient and without performance
penalty, AFAICS.

Regards,

Clemens

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

WARNING: multiple messages have this Message-ID (diff)
From: Clemens Koller <clemens.koller@anagramm.de>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: adaplas@gmail.com, linux-kernel@vger.kernel.org,
	linuxppc-dev@ozlabs.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Linux-fbdev-devel] [PATCH 1/2] fb: add support for foreign endianness
Date: Wed, 20 Feb 2008 16:43:42 +0100	[thread overview]
Message-ID: <47BC4AAE.8020908@anagramm.de> (raw)
In-Reply-To: <18363.31427.989835.105966@cargo.ozlabs.ibm.com>

Paul Mackerras schrieb:
> Andrew Morton writes:
> 
>> Bizarrely, the original author of the patch (Anton) has fallen off the cc. 
>> Could whoever did that please thwap himself?
>>
>> Anyway, my head is now officially spinning.  Did anyone actually have a
>> reason why we shouldn't proceed with Anton's patch?
> 
> I was wondering if it would be sufficient to provide alternative
> versions of fb_readl, fb_writel etc. that do byte-swapping.  That
> would mean that all framebuffers would have to have the same
> endianness, but that would suffice for embedded systems such as
> Anton's and would end up a lot simpler IMHO.

Yes. At least the affected PowerPC platforms can do byte-swapping on
the fly, so this should be sufficient and without performance
penalty, AFAICS.

Regards,

Clemens

WARNING: multiple messages have this Message-ID (diff)
From: Clemens Koller <clemens.koller@anagramm.de>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@linux-foundation.org>,
	adaplas@gmail.com, benh@kernel.crashing.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Anton Vorontsov <avorontsov@ru.mvista.com>
Subject: Re: [Linux-fbdev-devel] [PATCH 1/2] fb: add support for foreign endianness
Date: Wed, 20 Feb 2008 16:43:42 +0100	[thread overview]
Message-ID: <47BC4AAE.8020908@anagramm.de> (raw)
In-Reply-To: <18363.31427.989835.105966@cargo.ozlabs.ibm.com>

Paul Mackerras schrieb:
> Andrew Morton writes:
> 
>> Bizarrely, the original author of the patch (Anton) has fallen off the cc. 
>> Could whoever did that please thwap himself?
>>
>> Anyway, my head is now officially spinning.  Did anyone actually have a
>> reason why we shouldn't proceed with Anton's patch?
> 
> I was wondering if it would be sufficient to provide alternative
> versions of fb_readl, fb_writel etc. that do byte-swapping.  That
> would mean that all framebuffers would have to have the same
> endianness, but that would suffice for embedded systems such as
> Anton's and would end up a lot simpler IMHO.

Yes. At least the affected PowerPC platforms can do byte-swapping on
the fly, so this should be sufficient and without performance
penalty, AFAICS.

Regards,

Clemens

  parent reply	other threads:[~2008-02-20 15:44 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 15:44 [PATCH 1/2] fb: add support for foreign endianness Anton Vorontsov
2008-02-05 19:07 ` Anton Vorontsov
2008-02-15  6:49 ` Andrew Morton
2008-02-15  6:49   ` Andrew Morton
2008-02-15  6:49   ` Andrew Morton
2008-02-15 16:45   ` Anton Vorontsov
2008-02-15 16:45     ` Anton Vorontsov
2008-02-17  9:44     ` Geert Uytterhoeven
2008-02-17  9:44       ` [Linux-fbdev-devel] " Geert Uytterhoeven
2008-02-17  9:44       ` Geert Uytterhoeven
2008-02-18  7:18       ` Krzysztof Helt
2008-02-18  7:18         ` [Linux-fbdev-devel] " Krzysztof Helt
2008-02-18  7:18         ` Krzysztof Helt
2008-02-18 17:30         ` Valdis.Kletnieks
2008-02-18 17:30           ` [Linux-fbdev-devel] " Valdis.Kletnieks
2008-02-18 17:30           ` Valdis.Kletnieks
2008-02-18 17:37           ` Anton Vorontsov
2008-02-18 17:37             ` [Linux-fbdev-devel] " Anton Vorontsov
2008-02-18 17:37             ` Anton Vorontsov
2008-02-18 23:35           ` Clemens Koller
2008-02-18 23:35             ` Clemens Koller
2008-02-19  0:35             ` Benjamin Herrenschmidt
2008-02-19  0:35               ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2008-02-19 11:27               ` Clemens Koller
2008-02-19 12:05                 ` Andrew Morton
2008-02-19 12:05                   ` [Linux-fbdev-devel] " Andrew Morton
2008-02-19 12:05                   ` Andrew Morton
2008-02-19 12:22                   ` Clemens Koller
2008-02-19 12:22                     ` Clemens Koller
2008-02-20  0:47                   ` Valdis.Kletnieks
2008-02-20  0:47                     ` Valdis.Kletnieks
2008-02-20  0:50                     ` Benjamin Herrenschmidt
2008-02-20  0:50                       ` Benjamin Herrenschmidt
2008-02-20  0:56                   ` Paul Mackerras
2008-02-20  0:56                     ` Paul Mackerras
2008-02-20 12:18                     ` Anton Vorontsov
2008-02-20 12:18                       ` Anton Vorontsov
2008-02-20 20:38                       ` Benjamin Herrenschmidt
2008-02-20 20:38                         ` Benjamin Herrenschmidt
2008-02-21  4:59                       ` Paul Mackerras
2008-02-21  4:59                         ` Paul Mackerras
2008-02-20 15:43                     ` Clemens Koller [this message]
2008-02-20 15:43                       ` Clemens Koller
2008-02-20 15:43                       ` Clemens Koller
2008-02-16 11:49 ` Benjamin Herrenschmidt
2008-02-16 11:49   ` Benjamin Herrenschmidt

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=47BC4AAE.8020908@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=adaplas@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.