From: Nikolai Zhubr <n-a-zhubr@yandex.ru>
To: Leo Li <pku.leo@gmail.com>
Cc: support@amlogic.com, linux-usb@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, openwrt-devel@lists.openwrt.org,
Peter Chen <hzpeterchen@gmail.com>
Subject: Re: Driver(s) for Synopsys' DesignWare USB OTG
Date: Mon, 09 Jan 2012 16:44:00 +0400 [thread overview]
Message-ID: <4F0AE110.7010106@yandex.ru> (raw)
In-Reply-To: <CADRPPNRLKhDEU=mVDjbxaNtOD+665hQodhQzpVBc11120GpuJQ@mail.gmail.com>
Hello Leo,
09.01.2012 9:17, Leo Li:
> On Sun, Jan 8, 2012 at 8:56 PM, Nikolai Zhubr<n-a-zhubr@yandex.ru> wrote:
>>> 2012/1/8 Nikolai Zhubr<n-a-zhubr@yandex.ru>:
>>>>
>>>> Hello developers,
>>>>
>>>> I'm trying to find/combine/fix a driver for Synopsys' DesignWare USB
>>>> controller. This thing is USB 2.0 host/slave/otg capable and is used in
>>>> various SoCs including Amlogic 8726M, Ralink RT305x, and probably more.
>>>>
[...trim...]
>
> I think the challenge of cooperation in situation like this is that
> most companies don't like to advertise the source of the licensed IP
> block. Even the owner of the IP block doesn't list all users of the
> block(maybe business requirement). It was really hard to find out if
> the same IP has been used by anyone else. Also the owner of this USB
> IP block has been changed for several times(ARC, TDI, ChipIdea, and
> Synopsys) which made it even more difficult to tell.
Ah, I see. It explains.
But communicating in private and keeping some public repository up to
date would still be allowed I suppose?
>
>>
>>
>>> I am not sure we can combine all Synopsys USB drivers to single file, but
>>> we
>>
>>
>> Synopsys driver which I examine consists of 16 files (each of 2 versions),
>> 200k lines total. I've already perpared some few smaller files for version
>> merging. So probably it is doable, but quite a lot of work, therefore I
>> wouldn't like it to be wasted.
>
> I didn't examine the Synopsys driver myself. But if it is so complex
> as you described, it might be better to start with the in-tree drivers
> IMO.
Unfortunately its far beyond my capabilities at the moment. Besides, it
looks like huge effort has already been invested into the existing
driver, so to me it seems fixing it rather than starting from scratch
would be more realistic anyway (unless a company with unlimited
resources step in...)
Thank you.
Nikolai.
>
> - Leo
>
>
prev parent reply other threads:[~2012-01-09 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 17:30 Driver(s) for Synopsys' DesignWare USB OTG Nikolai Zhubr
2012-01-08 3:12 ` Peter Chen
2012-01-08 12:56 ` Nikolai Zhubr
2012-01-09 2:12 ` Peter Chen
2012-01-09 12:41 ` Nikolai Zhubr
2012-01-09 5:17 ` Leo Li
2012-01-09 12:44 ` Nikolai Zhubr [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=4F0AE110.7010106@yandex.ru \
--to=n-a-zhubr@yandex.ru \
--cc=hzpeterchen@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=pku.leo@gmail.com \
--cc=support@amlogic.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.