linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: "Kimble, James" <jkimble@harris.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Epson S1D13A04 video driver
Date: Thu, 6 Nov 2008 23:21:48 +0100	[thread overview]
Message-ID: <20081106232148.f9a93954.kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <0AF7234EE71C18419A2CFFFB8EF9C17CD43412@cine2k1.cs.myharris.net>


[-- Attachment #1.1: Type: text/plain, Size: 4157 bytes --]

On Thu, 6 Nov 2008 15:52:51 -0500
"Kimble, James" <jkimble@harris.com> wrote:

> 
> 
> On Thu, 6 Nov 2008 03:50:43 -0500
> "Kimble, James" <jkimble@harris.com> wrote:
> 
> >On Thu, 6 Nov 2008 03:44:43 +0100
> >"Kristoffer Ericson" <kristoffer.ericson@gmail.com> wrote:
> >
> >>On Thu, 6 Nov 2008 07:40:43 -0500
> >>"Kimble, James" <jkimble@harris.com> wrote:
> >
> >> 
> >> I'm working on project that needs to utilize the Epson S1D13A04
> device
> >> on a Coldfire processor based system running the Linux 2.6.25 kernel.
> >> The driver I see in the kernel sources had the name of Thibaut Varene
> in
> >> it and he told me you are the current maintainer of this driver.
> >
> >I took maintainership as of 2.6.27. I've CC'ed linux-fb since thats the
> >relevant mailinglist.
> >
> 
> Ok. Thanks.
> 
> >> 
> >> The driver in the 2.6.25 kernel supports the s1d13xxx series of chips
> >> but there's a good deal of variation in this series (register
> >> assignments and sizes, memory size, etc.). Can you tell me if there
> is a
> >> driver more specific to my chip (the S1D13A04)? I've begun the
> process
> >> of porting the existing driver to work with my chip but it's a pain.
> I'm
> >> really trying to save myself some time.
> >
> >Without looking at datasheets of your platform I would say that
> >you would be best of sticking with the s1d13xxx driver. The reason for
> >me taking maintainership is that there have been very little progress
> in
> >the driver for the last year and it's in need of updates. The goal
> >is to make it a truly 13xxx driver.
> >
> >So far I've started to familiarize myself with the driver and also
> >added some revision detection (it was locked to one revision). 
> >
> >If there is something obvious lacking in the resources supplied
> >to the driver thats where I would start. Can you give some more
> specific
> >details on what you need?
> 
> 
> Well, as you know the drivers history has been to be very specific to a
> single chip. The driver for the 2.6.9 kernel was and the driver for the
> 2.6.25 kernel is also. I ported the 2.6.9 version to the 2.6.10 kernel 
> and modified it to work with the S1D13A04 device. Not a lot of work but 
> I definately had to get a good understanding of the frame buffer section
> 

If you got any diffs against the 2.6.10 kernel it would be a good start.
It would be interesting to see where the changes are needed.

> of the kernel (never been there before) and of this specific driver. It 
> appears there's no less work to do for the very different but no less 
> specific s1d13xxxfb driver in the 2.6.25 kernel. Notes in the driver 
> itself indicate that though it's a driver that's general to the s1d13 
> class of chips it will only work with one of the later versions. 
> 
> I would just say it would be really nice to get this driver cabable of 
> handling more than one device. Not a critisism just a wish. Sigh....

Thats the general idea. I'm very eager to get it more generic (=support more).

> 
> 
> >
> >Best wishes
> >Kristoffer
> >
> >> 
> >> Any help or documentation you can offer would be greatly appreciated.
> >
> >By documentation you mean? If you are looking for examples using the
> >driver you can check jornada720.c. It should give a clear picture
> >of howto supply the driver with framebuffer, memory areas and also
> >some register initial values.
> >
> 
> Sure and it was helpful. I found that based on some searches and some
> help from Geert Oyterhoeven (thanks guy). I'm well on my way to getting
> the port done (I think) I was just hoping (there I go again...) that 
> there might be a dead ringer I could just install and go with. I know...
> at least I got some more experience with the frame buffer system....

Just give me a diff what you needed to do and we can figure out
howto give you out-of-the-box working fb.

> 
> Thanks for your time. I do appreciate it.

No worries, please keep me posted on your progress.

> 
> >> 
> >> Thanks,
> >> 
> >> James Kimble


-- 
Kristoffer Ericson <kristoffer.ericson@gmail.com>

[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 182 bytes --]

_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel

      reply	other threads:[~2008-11-06 21:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0AF7234EE71C18419A2CFFFB8EF9C17CD431C1@cine2k1.cs.myharris.net>
2008-11-06 20:43 ` Epson S1D13A04 video driver Kristoffer Ericson
2008-11-06 20:52   ` Kimble, James
2008-11-06 22:21     ` Kristoffer Ericson [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=20081106232148.f9a93954.kristoffer.ericson@gmail.com \
    --to=kristoffer.ericson@gmail.com \
    --cc=jkimble@harris.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).