From: Macpaul Lin <macpaul.lin@mediatek.com>
To: Lars Melin <larsm17@gmail.com>
Cc: Oliver Neukum <oneukum@suse.com>,
Andrey Arapov <andrey.arapov@gmail.com>,
Johan Hovold <johan@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Mediatek WSD Upstream <wsd_upstream@mediatek.com>,
<linux-usb@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v5] cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader.
Date: Wed, 19 Dec 2018 01:48:23 +0800 [thread overview]
Message-ID: <1545155303.16619.11.camel@mtkswgap22> (raw)
In-Reply-To: <5b0e5bf4-0411-0c58-ccae-fe66c937a36b@gmail.com>
On Tue, 2018-12-18 at 23:42 +0700, Lars Melin wrote:
> On 12/18/2018 22:19, Macpaul Lin wrote:
>
>
> > Hi all,
> >
> > After double check the PID/VID officially used (registered) by Mediatek
> > Inc. The following VID/PID maps to the corresponding USB interface of
> > the firmware of cell phone.
> > VID:0x0e8d, PID:0x0003: Mediatek BROM.
> > VID:0x0e8d, PID:0x2000: Mediatek Preloader.
> >
> > I will update Patch v6 for changing Andrey's previous comments.
> >
>
> You should show us a verbose lsusb of your 0e8d:0003 before changing
> Andrey's submission.
>
>
> Season's Greeting
> Lars
Hi Lars, Oliver, and Johan,
Well, it's about 1:30 a.m. here in Taiwan. I can do lsusb dump tomorrow
in Mediatek's office.
But there are a lot of tutorials about hacking and flash method of
customized firmware over the WWW. I can find one of the tutorial shows
these VID/PID combinations has been used since 2014.
(Actually they've been registered officially earlier than 2014.)
For example, please check the reference tutorial:
https://mattboyer.github.io/PYaffs/2014/07/31/Hacklog%233.html
You can check lsusb dump in this picture.
https://mattboyer.github.io/PYaffs/images/03_device_usbview.png
Both VID/PID of Mediatek BROM and Preloader can be found in INF file
pasted in this tutorial, too.
Sorry for the proprietary information policy I cannot paste them all,
but the VID/PID set of BROM and Preloader are just exactly the same
as described in this tutorial.
Thanks!
Regards,
Macpaul Lin
next prev parent reply other threads:[~2018-12-18 17:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1544671676-23912-1-git-send-email-macpaul.lin@mediatek.com>
2018-12-18 5:00 ` [PATCH v2] cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader Macpaul Lin
2018-12-18 9:02 ` Johan Hovold
2018-12-18 10:41 ` [PATCH v3] " Macpaul Lin
2018-12-18 10:54 ` Johan Hovold
2018-12-18 11:38 ` [PATCH v4] " Macpaul Lin
2018-12-18 11:44 ` Johan Hovold
2018-12-18 11:59 ` [PATCH v5] " Macpaul Lin
2018-12-18 12:38 ` Johan Hovold
2018-12-18 13:37 ` Oliver Neukum
2018-12-18 14:26 ` Macpaul Lin
2018-12-18 15:19 ` Macpaul Lin
2018-12-18 16:42 ` Lars Melin
2018-12-18 17:48 ` Macpaul Lin [this message]
2018-12-19 0:45 ` Lars Melin
2018-12-19 2:22 ` Macpaul Lin
2018-12-19 3:16 ` Macpaul Lin
2018-12-19 3:31 ` Lars Melin
2018-12-19 4:03 ` Macpaul Lin
2018-12-19 8:56 ` Oliver Neukum
2018-12-20 15:19 ` Greg Kroah-Hartman
2018-12-18 15:37 ` [PATCH v6] " Macpaul Lin
2018-12-19 4:11 ` [PATCH v7] " Macpaul Lin
2018-12-19 9:00 ` Johan Hovold
2018-12-20 15:28 ` Oliver Neukum
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=1545155303.16619.11.camel@mtkswgap22 \
--to=macpaul.lin@mediatek.com \
--cc=andrey.arapov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=larsm17@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=stable@vger.kernel.org \
--cc=wsd_upstream@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox