From: Wolfgang Denk <wd@denx.de>
To: Matthias Transier <matthias.transier@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Segmentation fault with X.org and Coral-P drivers
Date: Wed, 04 Jan 2006 22:10:03 +0100 [thread overview]
Message-ID: <20060104211003.EED51352ADF@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 04 Jan 2006 17:19:42 +0100." <b789c2e60601040819j65eea749p@mail.gmail.com>
Dear Matthias,
in message <b789c2e60601040819j65eea749p@mail.gmail.com> you wrote:
>
> > and EP5200 and Lite5200 are two different boards.
>
> Ok, my fault. I saw a Lite5200 on a picture somewhere and it looked
> pretty much like my EP board :-). But what I can tell for sure is:
> when I remove the "Embedded Planet" sticker on the board, there is a
> Freescale logo and a print (directly on the board): "IceCube Version
> 103"
Ouch. So far for marketing methods. I didn't know this.
> > Our kernel does not include any support for the EP5200 board.
>
> I checked it out from CVS, configured it, and it works (besides the X11 thing).
It should work on the Lite5200 board. I just expected different
hardware ...
> I did not use the prebuilt binaries, but I was able to compile the
I see.
> driver within my x.org tree. (I had to adapt the Imakefiles by myself,
> the provided ones were too different from the originals.)
If you want to send me your patches: they are welcome.
> The last line is a message that I added. Since the output stops at
> that point, it must be the next call that fails
> (mb86290_driver.c:604):
>
> if (!xf86I2CProbeAddress(fPtr->I2C, I2C_SAA7113))
> return FALSE;
>
> May that be a problem with the i2c driver in the kernel which does not
> exactly fit with my board?
This is not the kernel's (MPC5200) I2C driver; actually I2C is only
needed for external video decoder chip that _may_ be connected to the
CoralP chip. It is the CoralP itself that acts as an I2C "adapter" in
this case. By writing to some CoralP registers, accessible from the
host (CPU) via PCI, the driver manipulates external pins of the
CoralP chip, which form the I2C bus. It is an external (relative to
both CoralP and the CPU) device that is controlled through I2C; in
your case the Philips SA71111 video decoder chip.
> The following message also appears in Xorg.0.log, some lines above:
> (II) MB86290(0): I2C bus "MB86290 I2C bus" removed.
>
> Thanks in advance for any hint that you can give me.
You can disable video capture support, and thus the I2C, by setting
option "Video" to "no" in the driver's X11 config file:
Section "Device"
Identifier "MB86290 card"
Driver "mb86290"
Option "Video" "no"
EndSection
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Artificial Intelligence is the study of how to make real computers
act like the ones in movies.
prev parent reply other threads:[~2006-01-04 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 11:33 Segmentation fault with X.org and Coral-P drivers Matthias Transier
2006-01-04 15:48 ` Wolfgang Denk
2006-01-04 16:19 ` Matthias Transier
2006-01-04 17:59 ` Matthias Transier
2006-01-04 21:11 ` Wolfgang Denk
2006-01-04 21:10 ` Wolfgang Denk [this message]
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=20060104211003.EED51352ADF@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=matthias.transier@gmail.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 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).