kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: srinivas.pandruvada@linux.intel.com (Srinivas Pandruvada)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Status/Progress of CherryTrail / BayTrail support in mainline Linux kernel
Date: Mon, 12 Sep 2016 09:28:14 -0700	[thread overview]
Message-ID: <1473697694.154359.145.camel@linux.intel.com> (raw)
In-Reply-To: <20160911071905.GA21015@kroah.com>

On Sun, 2016-09-11 at 09:19 +0200, Greg KH wrote:
> On Mon, Sep 05, 2016 at 10:49:08AM +0200, Hanno Zulla wrote:
> > 
> > Hi,
> > 
> > sorry for asking a possibly obvious question, but:
> > 
> > Why is support for Cherry Trail / Bay Trail so bad in the mainline
> > kernel? Is this being worked on? And where can one help or track
> > the
> > progress with improving this?
> 
> Works for me! :)
Same here.
I also have three 2 BayTrail and one CherryTrail laptops, which I use
latest upstream kernel to test before sending change.

> 
> > 
> > Recently, I bought a Win10 netbook to install Linux on. It's a
> > beautiful small device with a fanless Z3735F CPU. Just right for my
> > kids as their first own computer.
> > 
> > After using Intel hardware since several years without a hitch, it
> > was
> > surprising to find this not being fully supported by current 2016
> > Linux
> > distributions.
I always use latest kernel. The problem is third party devices like
WiFi, touchpad etc.
As GKH suggested enter bugs, if the problem is in Intel SoC, we always
address.


Thanks,
Srinivas

  reply	other threads:[~2016-09-12 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  8:49 Status/Progress of CherryTrail / BayTrail support in mainline Linux kernel Hanno Zulla
2016-09-11  7:19 ` Greg KH
2016-09-12 16:28   ` Srinivas Pandruvada [this message]
2016-09-12 16:55     ` Hanno Zulla

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=1473697694.154359.145.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).