From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Hayes Wang" <hayeswang@realtek.com>,
nicfae@realtek.com, wlanfae@realtek.com, pctech@realtek.com,
security@realtek.com, "Hans de Goede" <hdegoede@redhat.com>,
"linux-realtek-soc@lists.infradead.org"
<linux-realtek-soc@lists.infradead.org>,
"Oder Chiou" <oder_chiou@realtek.com>,
Pkshih <pkshih@realtek.com>, nic_swsd <nic_swsd@realtek.com>,
"Derek [方德義]" <derek.fang@realtek.com>,
Kailang <kailang@realtek.com>,
linux-iio <linux-iio@vger.kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"info@ayaneo.com" <info@ayaneo.com>,
meakyi@ayaneo.com, software@ayaneo.com
Subject: Re: BMI160 accelerometer on AyaNeo tablet
Date: Sun, 23 Jan 2022 19:22:46 +0200 [thread overview]
Message-ID: <CACAwPwatbMjd9CLdFCWnND3FqT5ZtPJqEVC-Ohze+GoJ6ODqqw@mail.gmail.com> (raw)
In-Reply-To: <Yeh564iHDXEzHXUQ@smile.fi.intel.com>
Added software@ayaneo.com to CC ( I found this email on google).
Best regards,
Maxim Levitsky
On Wed, Jan 19, 2022 at 10:53 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> +Cc: more Aya-Neo emails (please, share it with your legal, involved managers
> and engineers).
>
> On Wed, Jan 19, 2022 at 09:05:25PM +0200, Maxim Levitsky wrote:
> > > Any news from Aya-Neo? Have you fixed and issued a new firmware, please?
> >
> > Nothing I heard of. Anything I can do to further help with this?
>
> Unfortunately we need to hear from the Aya-Neo, if they ever care about their
> products. Without that it would make an unfortunate precedent which will open
> a Pandora's box (means a green light on abusing ACPI specification and other's
> IPs, yes, Intellectual Property in this case, as ID is an IP of the corresponding
> vendor).
>
> I'm fine if Realtek doesn't care about their IDs to be (ab)used by somebody else,
> the main problem here is on Aya-Neo side.
>
> Is there any engineer-to-engineer connection with Aya-Neo? Because using that
> info@ address may be simply ignored / went to spam / etc.
>
> > On Tue, Nov 16, 2021 at 7:50 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > >
> > > I filed the form, Cc'ed this to more people from Realtek, still no response on
> > > the topic. Does Realtek really cares about their IDs?
> > >
> > > Any news from Aya-Neo? Have you fixed and issued a new firmware, please?
> > >
> > > On Wed, Oct 20, 2021 at 02:21:04PM +0300, Andy Shevchenko wrote:
> > > > +Cc: another set of emails from Realtek as per Hayes' email.
> > > >
> > > > Please waterfall to the people inside Realtek who can answer the question.
> > > > (Note, you may access this discussion in full via:
> > > > https://lore.kernel.org/linux-iio/CACAwPwYQHRcrabw9=0tvenPzAcwwW1pTaR6a+AEWBF9Hqf_wXQ@mail.gmail.com/T/#u)
> > > >
> > > > The problem here is to have an official confirmation of what 10ec:5280
> > > > ID is from Realtek's point of view.
> > > >
> > > > Context: the current discussion and a patch state that it's related
> > > > to gyro sensor. Is it so?
> > > >
> > > > On Wed, Oct 20, 2021 at 10:36:12AM +0300, Andy Shevchenko wrote:
> > > > > On Wednesday, October 20, 2021, Hayes Wang <hayeswang@realtek.com> wrote:
> > > > > > Andy Shevchenko <andy.shevchenko@gmail.com>
> > > > > > > Sent: Tuesday, October 19, 2021 5:59 PM
> > > >
> > > > ...
> > > >
> > > > > > > > > Realtek probably should make this ID marked somehow broken and not
> > > > > > use
> > > > > > > > > in their products in case the answer to the first of the above
> > > > > > question
> > > > > > > > > is "yes". (Of course in case the ID will be used for solely PCI
> > > > > > enumerated
> > > > > > > > > product there will be no conflict, I just propose to be on the
> > > > > > safest side,
> > > > > > > > > but remark should be made somewhere).
> > > > > > >
> > > > > > > Any comments from Realtek, please?
> > > > > >
> > > > > > Excuse me. I don't know this device, so I don't know who I could forward.
> > > > > > Maybe you could try our contract window from our web site.
> > > > > > https://www.realtek.com/en/cu-1-en/cu-1-taiwan-en
> > > > >
> > > > > Thanks for reply. I will try my best, but I am afraid that what you suggest
> > > > > will be a long loop (and I believe the people behind that form are not
> > > > > technical, they probably won’t understand the topic). I think you may pull
> > > > > strings inside much faster. Just ask somebody who is technical superior in
> > > > > your team / organization. Ideally inside company you may have a dedicated
> > > > > people who responsible for allocating PCI and ACPI IDs.
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
next prev parent reply other threads:[~2022-01-23 17:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACAwPwb7edLzX-KO1XVNWuQ3w=U0BfA=_kwiGCjZOpKfZpc2pw@mail.gmail.com>
2021-10-16 16:27 ` BMI160 accelerometer on AyaNeo tablet Maxim Levitsky
2021-10-17 10:58 ` Jonathan Cameron
2021-10-18 7:40 ` Andy Shevchenko
2021-10-18 15:17 ` Jonathan Cameron
2021-10-18 15:22 ` Andy Shevchenko
2021-10-18 15:30 ` Andy Shevchenko
2021-10-18 18:02 ` Maxim Levitsky
2021-10-18 19:02 ` Andy Shevchenko
2021-10-18 20:42 ` Maxim Levitsky
2021-10-19 9:58 ` Andy Shevchenko
2021-10-19 16:29 ` Maxim Levitsky
2021-10-20 2:31 ` Hayes Wang
[not found] ` <CAHp75VfB2FULb_jfQNg0wF9Z4jPkrKfmw6hSwtLg8Y1NhKks8g@mail.gmail.com>
2021-10-20 11:21 ` Andy Shevchenko
2021-11-16 17:49 ` Andy Shevchenko
2022-01-19 19:05 ` Maxim Levitsky
2022-01-19 20:51 ` Andy Shevchenko
2022-01-23 17:22 ` Maxim Levitsky [this message]
2022-02-02 16:23 ` Andy Shevchenko
2021-10-20 17:37 ` Jonathan Cameron
2021-10-20 20:03 ` Andy Shevchenko
2021-10-19 8:10 ` Hans de Goede
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=CACAwPwatbMjd9CLdFCWnND3FqT5ZtPJqEVC-Ohze+GoJ6ODqqw@mail.gmail.com \
--to=maximlevitsky@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=derek.fang@realtek.com \
--cc=hayeswang@realtek.com \
--cc=hdegoede@redhat.com \
--cc=info@ayaneo.com \
--cc=kailang@realtek.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=meakyi@ayaneo.com \
--cc=nic_swsd@realtek.com \
--cc=nicfae@realtek.com \
--cc=oder_chiou@realtek.com \
--cc=pctech@realtek.com \
--cc=pkshih@realtek.com \
--cc=security@realtek.com \
--cc=software@ayaneo.com \
--cc=wlanfae@realtek.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;
as well as URLs for NNTP newsgroup(s).