All of lore.kernel.org
 help / color / mirror / Atom feed
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: Future of S3C6410 platform
Date: Mon, 04 Jul 2011 21:14:19 +0200	[thread overview]
Message-ID: <2635745.FvrjgPkNLz@flatron> (raw)

List,

I am writing to ask what is the planned future for the (now obsolete?) S3C6410 
platform. Is there any ongoing work on bringing more feature-complete support 
for it?

The platform is really far behind its newer friends and here is what bothers 
me most:
- missing basic features as NOHZ support
- buggy drivers (in mainline!, s3c-fb requesting irq before fully initializing 
driver data, same goes for the adc driver)
- totally broken usb gadget driver - I could not get it to work on my platform 
in any way (Samsung GT-i5700 phone; I am getting a Tiny6410 soon, so I will 
check whether it is not a board specific issue) without rewriting control 
endpoint handling code, not even mentioning about DMA support, which I still 
cannot get to work
- poor OneNAND support (mostly in terms of performance)
- no power domain support
- no support for advanced features of the chip (ie. functionality provided by 
old, and really _bad_, s3c modules)

I have already added NOHZ support, fixed fb and adc bugs, refactored control 
endpoint handling in udc driver (no DMA yet), done some improvement to OneNAND 
driver (still a big work in progress though, this is a topic for another 
message) and implemented power domain management + other minor changes/fixes. 

All of this is available in my tree at 
git://github.com/tom3q/spica-2.6.38.git, but I am going to prepare patches 
containing all the changes a bit later, after I rebase all my work to latest 
Linux sources, as I worked mostly on Android 2.6.38 sources.

Best regards,
Tomasz Figa

             reply	other threads:[~2011-07-04 19:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04 19:14 Tomasz Figa [this message]
2011-07-04 20:39 ` Future of S3C6410 platform Arnd Bergmann
2011-07-04 21:39   ` Ben Dooks
2011-07-04 23:10     ` Tomasz Figa
2011-07-04 23:25       ` Russell King - ARM Linux
2011-07-04 23:40         ` Tomasz Figa

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=2635745.FvrjgPkNLz@flatron \
    --to=tomasz.figa@gmail.com \
    --cc=linux-arm-kernel@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.