linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Stefan Nickl <Stefan.Nickl@kontron.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Lite5200 PCI not working
Date: Thu, 01 Jul 2004 10:52:56 +0200	[thread overview]
Message-ID: <20040701085301.3741AC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 01 Jul 2004 10:41:05 +0200." <1088671264.6226.59.camel@lucy.pep-kaufbeuren.de>


In message <1088671264.6226.59.camel@lucy.pep-kaufbeuren.de> you wrote:
> On Mon, 2004-06-21 at 18:20, Kate Alhola wrote:
> > >Are you really sure? Maybe it was just an issue of finding the  right
> > >jumper  settings (which is non-trivial). We tested both with Rev. 4.0
> > >and Rev. 5.0 cards, and didn't need -12V.
>
> Hi,
>
> seems I'm also stuck with this non-trivial problem here.
> I have a Rev.5 card, and just discovered the three jumpers
> to override the analog MUX (J250-252).
>
> I get a picture now, but it's *very* dim, and the colors
> seem not quite right when the CRT's brightness is .
>
> Are there any more jumpers to set or could this be an
> issue with the driver (linuxppc_2_4_devel -Dyesterday)?
> Or maybe is the MUXer also a neccessary booster?

OK. Please see http://www.denx.de/twiki/bin/view/DULG/CoralPInstallation

It includes two images (for Rev. 4.0 and Rev. 5.0 cards)  taken  from
working systems.

I'll need to update the table to represent the differences.

Hope this gets you started.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Newer disks don't have a rectangular layout anymore,  but  Unix  (and
SunOS) still assumes this.     - Peter Koch in <koch.779356598@rhein>

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

  reply	other threads:[~2004-07-01  8:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 10:03 Lite5200 PCI not working Iñigo Lopez Barranco
2004-06-21 10:26 ` Gerhard Jaeger
2004-06-21 10:53   ` Wolfgang Denk
2004-06-21 11:39     ` Gerhard Jaeger
2004-06-21 14:12     ` Kate Alhola
2004-06-21 15:14       ` Wolfgang Denk
2004-06-21 16:20         ` Kate Alhola
2004-07-01  8:41           ` Stefan Nickl
2004-07-01  8:52             ` Wolfgang Denk [this message]
2004-06-21 10:51 ` Wolfgang Denk
2004-06-21 19:19 ` Mark Jonas
2004-06-22  6:08   ` Gerhard Jaeger
  -- strict thread matches above, loose matches on Subject: below --
2004-06-21 11:12 Iñigo Lopez Barranco
2004-06-21 11:48 ` Gerhard Jaeger
2004-07-01  9:18 Wolfgang Denk
2004-07-01 11:36 ` Kate Alhola
2004-07-01 12:38   ` Stefan Nickl
2004-07-01 22:20     ` Kate Alhola
2004-07-01 22:29       ` Wolfgang Denk
2004-07-02  4:43         ` Kate Alhola
2004-07-02  7:22           ` Wolfgang Denk
2004-07-02  7:55             ` Kate Alhola
2004-07-02  8:51               ` Wolfgang Denk
2004-07-08 11:57             ` Stefan Nickl
2004-07-08 12:12               ` Wolfgang Denk
     [not found] <20040708124140.E18E4C109F@atlas.denx.de>
2004-07-08 13:34 ` Stefan Nickl

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=20040701085301.3741AC109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Stefan.Nickl@kontron.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).