From: Pavel Machek <pavel@ucw.cz>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
"Miguel Oliveira" <cmroliv@gmail.com>,
"Pali Rohár" <pali.rohar@gmail.com>,
"kernel list" <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: patch "staging: remove nokia_hp4p driver
Date: Wed, 3 Dec 2014 13:33:36 +0100 [thread overview]
Message-ID: <20141203123336.GA31708@amd> (raw)
In-Reply-To: <4CA4FD0A-C167-4A12-A137-766CB3A2D5D5@holtmann.org>
Hi!
> > "These are a lot of public functions. Are they all really needed or can
> > the code be done smart."
> >
> > in TODO file.
>
> so what about all the other really major details that needed fixing. I mean anybody who was compiling for OMAP platform could have fixed the tons and tons of inlines quickly.
>
Do you have n900 nearby? You are welcome to try...
Unfortunately, it is not exactly easy. v3.18 with USB patch works with
nfsroot, which makes development possible (good).
Some core (or omap) change broke h4p between 3.15 and 3.16. Bisect
will not be fun, I suspect.
> > (Also hopefully get some testing from
> > n900 community; code is more
> > visible in staging).
>
> The problem is that they are testing the wrong thing. And lets face it, we already knew this driver works since Nokia shipped it in products.
>
Except that it does not :-(. Apparently not even place in staging was
enough to get regular testing... but at least it will help bisect.
> > I attempted hdev->setup conversion, but could not figure it out till
> > now. Clearly it needs to be done.
> >
> > For doing that, it would be good to have userland to work with, and
> > yes it takes time. (Debugging on 4" screen sucks.)
>
> Actually hdev->setup does not need any userland. As long as request_firmware() works, you are just fine. And since the driver already uses that in the first place, I assume it works.
>
Without working serial port, you can't really debug without
userland. Not on machine that lacks shift-pgup.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2014-12-03 12:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14094295422869@kroah.com>
2014-08-30 21:30 ` patch "staging: remove nokia_hp4p driver Pavel Machek
2014-08-30 22:04 ` Greg KH
2014-08-30 22:44 ` Pavel Machek
2014-08-30 22:49 ` Greg KH
2014-08-31 9:28 ` Pavel Machek
2014-08-30 23:09 ` Marcel Holtmann
2014-08-31 8:23 ` Pali Rohár
2014-08-31 9:51 ` Pavel Machek
2014-09-01 22:16 ` Marcel Holtmann
2014-09-04 11:36 ` Pavel Machek
2014-12-03 12:33 ` Pavel Machek [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=20141203123336.GA31708@amd \
--to=pavel@ucw.cz \
--cc=cmroliv@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pali.rohar@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox