All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Global changelogs about
Date: Mon, 3 Mar 2008 00:59:31 +0000	[thread overview]
Message-ID: <20080303005931.GA25082@shareable.org> (raw)
In-Reply-To: <20080302180601.GA22003@xi.wantstofly.org>

Lennert Buytenhek wrote:
> On Sun, Mar 02, 2008 at 03:21:36PM +0000, Jamie Lokier wrote:
> 
> > (Alternatively, if anyone has forward-ported Sigma Designs ARM support
> > to 2.6 kernels, or would like to collaborate with me on that, I would
> > be _very_ interested...)
> 
> I don't have the hardware, but I can help.

You might have, but not know it, sitting near your TV (if you have one
of those archaic old things :-)  It's used in high-def media
player type devices.

> Are docs freely available?

Unfortunately there are no freely available docs that I'm aware of.
Even I don't have docs.

What I do have is GPL kernel code and patches, which can be published
in the usual way.

(Btw, all companies selling devices containing these chips running
Linux should provide the GPL kernel source or an offer of it.  Sigma
Designs themselves (the chip vendor) do provide it to their downstream
product makers, a README which indicates it is provided under GPL
terms, and I have confirmed with my upstream supplier that it is ok to
distribute.  But the consumer product makers and sellers that I'm
aware of don't seem to comply by passing it further along... making it
surprisingly hard to get from anyone.)

Unfortunately, the most interesting parts of this device (media
processing) are very well abstracted, so the kernel driver does
nothing more than pass along a few generic commands to that part.

So, the kernel source doesn't contain much that's interesting to
anyone not using these devices.  Just:

   - Serial port hacks.

   - Usual custom bits and pieces for the board, interrupts, etc.

   - PATA driver for the unusual Sigma Designs IDE interface and DMA
     engine.

   - Various drivers for other legacy things not used in current
     chips, e.g. their old ethernet interface.

   - Pass-through driver interfacing to binary blob to handle video,
     much of which runs on coprocessors on the same chip.

   - MTD modification which is necessary for correct erasing in
     cfd_cmdset_0002.c (which a bog standard CFI flash), and which
     surprises me that it's not in standard kernels, implying nobody
     else needs it.  (Note to self: talk about this sometime).

   - Parts of 2.5 MTD code back-ported, selectively.

   - I'm sure there's something else, but nothing to get excited by.

-- Jamie

      reply	other threads:[~2008-03-03  0:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 22:37 Global changelogs about Schlägl Manfred jun.
2008-02-28 23:50 ` Jörn Engel
2008-02-29  8:42   ` Schlägl Manfred jun.
2008-02-29  8:57     ` Jörn Engel
2008-02-29  9:19       ` Schlägl Manfred jun.
2008-02-29 14:53         ` Brijesh Singh
2008-02-29 15:26         ` Jörn Engel
2008-03-02 15:21       ` Jamie Lokier
2008-03-02 18:06         ` Lennert Buytenhek
2008-03-03  0:59           ` Jamie Lokier [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=20080303005931.GA25082@shareable.org \
    --to=jamie@shareable.org \
    --cc=buytenh@wantstofly.org \
    --cc=linux-mtd@lists.infradead.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.