linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: 21cnbao@gmail.com (Barry Song)
To: linux-arm-kernel@lists.infradead.org
Subject: s3c-hsotg driver problem
Date: Wed, 20 Jan 2010 16:13:16 +0800	[thread overview]
Message-ID: <3c17e3571001200013pfd622f6g8593b21a10649487@mail.gmail.com> (raw)
In-Reply-To: <4B530920.5020901@gmail.com>

On Sun, Jan 17, 2010 at 8:57 PM, Maurus Cuelenaere
<mcuelenaere@gmail.com> wrote:
> Op 17-01-10 03:00, Barry Song schreef:
>>
>> In fact, I once used 12Mhz ?external crystal, after setting PHYCLK
>> right, ?both USB 1.1 as host and 2.0 as gadget can work. The kernel
>> version I used is 2.6.28.
>>
>
> You say the kernel version you used is 2.6.28, I'm betting you weren't using
> Ben Dooks' driver then and this was Samsung's tree?
Yes.
> The kernel that is currently shipped with the device I'm porting for (SmartQ
> 7) is using 2.6.24, which also has Samsung's patches applied (and uses other
> drivers than in mainline).
Yes.
>
> AFAIK there are 2 (?) 'main' trees floating around with Samsung patches:
> 2.6.24 and 2.6.28, then there are 2.6.29 and 2.6.31 (and newer) trees which
> contain patches from a mix of both and mainline.
>
> What I'm looking for is getting everything to work with *mainline* drivers,
> so in the end I can push the SmartQ boards to mainline.
That needs many merge.
>
> Regards,
> Maurus Cuelenaere
>

      parent reply	other threads:[~2010-01-20  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16 12:39 s3c-hsotg driver problem Maurus Cuelenaere
2010-01-17  2:00 ` Barry Song
2010-01-17 12:57   ` Maurus Cuelenaere
2010-01-17 13:19     ` jassi brar
2010-01-20  8:13     ` Barry Song [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=3c17e3571001200013pfd622f6g8593b21a10649487@mail.gmail.com \
    --to=21cnbao@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 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).