All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Meriin" <Michael@KSWaves.com>
To: "Stefan Roese" <stefan.roese@esd-electronics.com>,
	"Laurent Mohin" <laurent.mohin@acterna.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: How to change endian attribute for a memory region
Date: Mon, 14 Oct 2002 12:18:33 +0200	[thread overview]
Message-ID: <023a01c2736b$0db250c0$450fa8c0@amitesting> (raw)
In-Reply-To: EFEAIMDCOOOHIEPHDNFJAENOEHAA.stefan.roese@esd-electronics.com


Stefan,

> why don't you use the MD4 signal of the Epson Chip to configure it as big
> endian device? Or am I missing something here?
>
> Best regards,
> Stefan.
>

First of all it is not my implementation problem :))
You are right you can use this signal,  but in my implementation for 13704
it was impossible to use it, because of other signals constrains:
 this signal was possible to be used only for 68000 bus.
So in our case (MPC855) we simply flipped the data bus, by the way only
after that we
found out that this solution was suggested by Epson too.

Best Regards,
                     Michael Meriin

> > Betreff: Re: How to change endian attribute for a memory region
> >
> >
> >
> > Michaêl,
> >
> > I can't connect the chip as a byte wide device due to performance
> > degradation.
> > Due to other constraints, I can't invert MSB and LSB. In fact,
> > due to color
> > mapping, if I work in 8 bit per pixel, I must address my
> > framebuffer in big
> > endian mode. In 16 bit per pixel, I need to use little endian mode.
> > So I really need to change the endian attribute.
> >
> > Thanks for your answer
> >
> > Laurent
> >
> >
> >
> >
> > "Michael Meriin" <Michael@KSWaves.com> on 14/10/2002 10:57:00
> >
> > To:    linuxppc-embedded@lists.linuxppc.org, Laurent
> >        Mohin/SE/Wavetek@Global
> > cc:
> > Subject:    Re: How to change endian attribute for a memory region
> >
> >
> >
> > > I'm trying to interface a 405GP chip with an EPSON S1D13506 graphic
> > > controller. Because the EPSON chip is a little endian, I need to have
my
> > > framebuffer memory acceded in little endian mode.
> > > What is the best way to change endian attribute for a specific memory
> > > region (ioremap little endian)?
> > >
> > > Laurent
> >
> > I suggest you to connect it to the uP as a byte wide device, this will
> > immediately solve your problem.
> > The second way you can do it for 16 bit bus to connect MSB and LSB wise
a
> > wiser.
> > >
> > Best Regards,
> >                      Michael Meriin
> >
> >
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-10-14 10:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15  9:08 How to change endian attribute for a memory region Laurent Mohin
2002-10-15  9:55 ` Stefan Roese
2002-10-14 10:18   ` Michael Meriin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-15 16:40 Ralph Blach
2002-10-15 15:00 Laurent Mohin
2002-10-15 15:45 ` Dan Malek
2002-10-15 14:57 Laurent Mohin
2002-10-15 14:34 Ralph Blach
2002-10-15 11:07 Laurent Mohin
2002-10-15 14:15 ` Matt Porter
2002-10-15 14:35   ` Allen Curtis
2002-10-15  8:42 Laurent Mohin
2002-10-14  8:57 ` Michael Meriin

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='023a01c2736b$0db250c0$450fa8c0@amitesting' \
    --to=michael@kswaves.com \
    --cc=laurent.mohin@acterna.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=stefan.roese@esd-electronics.com \
    /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.