The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ben Hutchings <ben@decadent.org.uk>,
	devel@driverdev.osuosl.org,
	Teddy Wang <teddy.wang@siliconmotion.com.cn>,
	Markos Chandras <Markos.Chandras@imgtec.com>
Subject: Re: [PATCH] Revert "staging: sm7xxfb: remove driver"
Date: Sat, 22 Nov 2014 12:32:02 +0530	[thread overview]
Message-ID: <20141122070202.GB4490@sudip-PC> (raw)
In-Reply-To: <20141120232329.GA27669@kroah.com>

On Thu, Nov 20, 2014 at 03:23:29PM -0800, Greg Kroah-Hartman wrote:
> On Thu, Nov 20, 2014 at 05:09:25PM -0500, Steven Rostedt wrote:
> > 
> > Someone reported a bug in the function graph tracer for MIPS. As I'm
> > still waiting on my USB serial for my Imagination MIPS board, I decided
> > to bring my Lemote Yeeloong laptop back up to the latest kernel. This
> > is where I noticed that the screen no longer displays anything.
> > 
> > I ran a bisect, which came across a staging commit that removed the
> > sm7xxfb driver. When I reverted it on a v3.18-rc5 kernel and booted it
> > on my Lemote laptop, the display worked again.
> > 
> > I then did a search for this commit and found that Debian reverted it
> > too. Seems that there's still some Debian users of this laptop. (RMS?)
> > 
> > What needs to be done to make this a "proper" driver? I can try to
> > support it, although I have no idea how it works :-)
> 
> Have you read the TODO file in this patch?  If you are willing to work
> on this, I'll be glad to apply it, but the reason I removed it was
> because no one had done anything with it for a very long time.
> 
> It needs a maintainer / developer, otherwise I can't take this.

i will like to help in this. Silicon Motion is still having SM712 in its product line and SM718 might also be a similar one.

now the problems (as i see) for me to help in the driver :
1) i am a newbie. though i have learnt a lot from the patches i sent , but still I am a newbie.
2) most important - I do not have the hardware. So from the TODO list dual head and 2D acceleration support will be tough without actually checking on the hardware.

thanks
sudip

> 
> thanks,
> 
> greg k-h
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2014-11-22  7:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 22:09 [PATCH] Revert "staging: sm7xxfb: remove driver" Steven Rostedt
2014-11-20 23:23 ` Greg Kroah-Hartman
2014-11-22  7:02   ` Sudip Mukherjee [this message]
2014-11-22 14:00     ` Greg Kroah-Hartman
2014-11-22 16:20       ` Sudip Mukherjee
2014-12-01  7:02         ` Sudip Mukherjee
2014-11-20 23:36 ` Ben Hutchings

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=20141122070202.GB4490@sudip-PC \
    --to=sudipm.mukherjee@gmail.com \
    --cc=Markos.Chandras@imgtec.com \
    --cc=ben@decadent.org.uk \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=teddy.wang@siliconmotion.com.cn \
    /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