All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>
Cc: "'Demke, Torsten'" <Torsten.Demke@fci.com>,
	"'linuxppc-embedded@ozlabs.org'" <linuxppc-embedded@ozlabs.org>,
	'Steven Blakeslee' <BlakesleeS@embeddedplanet.com>
Subject: Re: 2.6.10-rc3 for 8xx with I2C config enabled  still fails ...
Date: Fri, 17 Dec 2004 09:38:37 -0700	[thread overview]
Message-ID: <20041217163837.GE31110@smtp.west.cox.net> (raw)
In-Reply-To: <313680C9A886D511A06000204840E1CF0A6473AF@whq-msgusr-02.pit.comms.marconi.com>

On Fri, Dec 17, 2004 at 11:30:53AM -0500, Povolotsky, Alexander wrote:

> Hi,
> 
> Even so much "touted" ;-) 2.6.10-rc3 FAILS for 8xx with I2C config enabled 
> ... and our custom MPC885 based board is using a single 24C02 type I2C
> EEPROM, connected to the I2C bus ...
> 
> Does anyone of you has any input/experience about 2.6.10-rc3 functionality
> (this all relates to our card) of:
> SPI, HDLC, Entropia, Legerity, watchdog, NAND flash support,
> MTD with JFFS2 filesystem support and flash compatibility ??? (Any info will
> be much appreciated !)

So, your best bet to get 8xx I2C working is to grab the 'latest' from a
2.4 tree that has it working, and move it up.  In doing so, you may want
to kill 'i2c-rpx' and merge it all into the i2c-algo-8xx file.

[snip]
> CONFIG_8xx=y
CONFIG_BROKEN=y
as well.  Not that it's directly relevant (the 8xx breakage is in
something else), but..

-- 
Tom Rini
http://gate.crashing.org/~trini/

      reply	other threads:[~2004-12-17 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 16:30 2.6.10-rc3 for 8xx with I2C config enabled still fails Povolotsky, Alexander
2004-12-17 16:38 ` Tom Rini [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=20041217163837.GE31110@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=Alexander.Povolotsky@marconi.com \
    --cc=BlakesleeS@embeddedplanet.com \
    --cc=Torsten.Demke@fci.com \
    --cc=linuxppc-embedded@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.