All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Imre Deak <imre.deak@solidboot.com>,
	Komal Shah <komal.shah802003@gmail.com>
Cc: James Simmons <jsimmons@infradead.org>,
	Vladimir <vovan888@gmail.com>, Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Siemens sx1: merge framebuffer support
Date: Tue, 21 Nov 2006 16:47:25 +0000	[thread overview]
Message-ID: <20061121164723.GB8193@atomide.com> (raw)
In-Reply-To: <3a5b1be00611210734k79c81305q7b229139c2b17ef6@mail.gmail.com>

Hi,

* Komal Shah <komal.shah802003@gmail.com> [061121 15:35]:
> On 11/21/06, James Simmons <jsimmons@infradead.org> wrote:
> >
> >Can you post the framebufer driver to the framebuffer list. We like to do
> >peer review. Thank you :-)

It would be nice to get the framebuffer integrated. I think it would be
best if Imre submitted the patches as it's mostly his work.

Imre, do you have time to send the patches to framebuffer list? If not,
I can send them.

> >On Tue, 21 Nov 2006, Vladimir wrote:
> >
> >> 2006/11/20, Tony Lindgren <tony@atomide.com>:
> >> > * Pavel Machek <pavel@ucw.cz> [061118 18:16]:
> >> > > From: Vladimir Ananiev <vovan888@gmail.com>
> >> > >
> >> > > Framebuffer support for Siemens SX1; this is second big patch. (Third
> >> > > one will be mixer/sound support). Support is simple / pretty minimal,
> >> > > but seems to work okay (and is somehow important for a cell phone 
> >:-).
> >> >
> >> > Pushed to linux-omap. I guess you're planning to send the missing
> >> > Kconfig + Makefile patch for this?
> >> >
> >> > Also, it would be better to use omap_mcbsp_xmit_word() or
> >> > omap_mcsbsp_spi_master_xmit_word_poll() instead of OMAP_MCBSP_WRITE as
> >> > it does not do any checking that it worked. The aic23 and tsc2101
> >> > audio in linux-omap tree in general has the same problem.
> >> >
> >> > Regards,
> >> >
> >> > Tony
> >> >
> >>
> >> Hmm. McBSP3 in SX1 is used in "GPIO mode". The only line used is CLKX,
> >> so I think OMAP_MCBSP_WRITE would be enough. Am I wrong ?
> >> -
> 
> Again, framebuffer support patch is based on the omap framebuffer
> driver, which is not yet submitted to upstream/fbdevel list. sx1
> framebuffer support just fill up the hooks required by -omap fb driver
> framework.

Yes, but the framebuffer code is in pretty much ready to be sent
upstream :)

Regards,

Tony

  reply	other threads:[~2006-11-21 16:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-18 18:16 Siemens sx1: merge framebuffer support Pavel Machek
2006-11-20 19:04 ` Tony Lindgren
2006-11-21  7:06   ` Vladimir
2006-11-21  8:42     ` Komal Shah
2006-11-21 11:30       ` Pavel Machek
2006-11-21 15:04     ` James Simmons
2006-11-21 15:04       ` James Simmons
2006-11-21 15:34       ` Komal Shah
2006-11-21 16:47         ` Tony Lindgren [this message]
2006-11-22 12:08           ` Imre Deák
2006-11-24 11:02   ` Pavel Machek
2006-11-28  2:15     ` Tony Lindgren

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=20061121164723.GB8193@atomide.com \
    --to=tony@atomide.com \
    --cc=imre.deak@solidboot.com \
    --cc=jsimmons@infradead.org \
    --cc=komal.shah802003@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=vovan888@gmail.com \
    /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.