linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Murray Jensen <Murray.Jensen@cmst.csiro.au>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: I2C module problem on 8260
Date: Wed, 13 Feb 2002 17:43:57 +1100	[thread overview]
Message-ID: <1037.1013582637@msa.cmst.csiro.au> (raw)
In-Reply-To: Message from Wolfgang Denk <wd@denx.de> of "Wed, 13 Feb 2002 00:18:08 BST." <20020212231813.2D906109D7@denx.denx.de>


On Wed, 13 Feb 2002 00:18:08 +0100, Wolfgang Denk <wd@denx.de> writes:
>I've sent such patches to Tom Rini many months ago (starting  29  Aug
>2001),  and  in some iterations again and again. It's for 8xx only so
>far, but adaption for 82xx is just a small exercise.

Well, I have an i2c driver for the CPM which supports both 8xx and 8260
(and potentially anything else that has a CPM) in the same source (although
I still haven't got around to testing the 8xx code). I avoid the issue raised
here by using kmalloc(). The code works fine as a loadable module, and it
only allocates the dual port ram once, the first time the module is loaded.
Of course, it is called drivers/i2c/i2c{-algo,}cpm.c.

These patches (amongst a whole lot of others) were also submitted around that
same time. After much back and forth I was asked to post the patches to this
list, which I have been meaning to do for many months now.

Initially, I was asked to submit the i2c changes via the i2c driver people,
but I countered this by pointing out that they really couldn't care less
about driver code for embedded powerpc (CPM), since it will never run on
anything else (as opposed to a driver for a PCI card which may work on
multiple platforms). We really only submit our code back to them for the
sake of completeness.

>Unfortunately, this patch was always ignored (as some  others,  too),
>so I finally gave up.

Hmm.. I wonder if we are being too careful about allowing stuff into the
_devel tree - isn't that what its for? Development stuff that might break
things? Besides, there are already some changes that make it in that severely
break things for some platforms - we all just put up with it and fix the
problems as they arise (witness the recent change in operation of the get_irq
function - the 8260 platform hung during boot the first time interrupts were
enabled, and it stayed that way for many months until I finally decided to
track the problem down).

Now, I'm not criticising anyone's effort, decisions or contributions here,
simply discussing our operational policy in a calm manner in the hope that
things might be freed up a bit (of course I recognise the chaos that could
arise if all changes were simply immediately incorporated without question,
but there has to be a happy medium somewhere).

Anyway, I should get off my arse and post those patches - I think there
is some good stuff in them (but then I would, wouldn't I). Cheers!
								Murray...
--
Murray Jensen, CSIRO Manufacturing Sci & Tech,         Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia.         Fax: +61 3 9662 7853
Internet: Murray.Jensen@cmst.csiro.au  (old address was mjj@mlb.dmt.csiro.au)


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

  reply	other threads:[~2002-02-13  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 22:49 I2C module problem on 8260 Eric.Oosterhof
2002-02-12 23:10 ` Dan Malek
2002-02-12 23:18   ` Wolfgang Denk
2002-02-13  6:43     ` Murray Jensen [this message]
2002-02-12 23:21   ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2002-02-20 19:26 Eric.Oosterhof

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=1037.1013582637@msa.cmst.csiro.au \
    --to=murray.jensen@cmst.csiro.au \
    --cc=linuxppc-dev@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).