public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Rodriguez <frodriguez.developer@outlook.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kernel 3.17.0
Date: Wed, 29 Oct 2014 16:22:29 -0400	[thread overview]
Message-ID: <BLU437-SMTP410EC6A99298E0DDDAD898D9C0@phx.gbl> (raw)
In-Reply-To: <CAGfcS_=702Dk9irmbUCDYiOVe3c0uMKWzzCC3i9nM0CKyitc=g@mail.gmail.com>

On Friday 24 October 2014 7:22:24 AM Rich Freeman wrote:
> On Thu, Oct 23, 2014 at 11:53 PM, Fernando Rodriguez
> <frodriguez.developer@outlook.com> wrote:
> > On Monday 20 October 2014 10:59:52 AM Michael Mattes wrote:
> >> And that is because of the additional features? :-D
> >
> > I've had issues with the additional features too. Some of the USB serial
> > devices don't get detected. But this is fixed by disabling the Gentoo 
specific
> > options. I may be wrong but I think they're just configuration patches, not 
the
> > actual kernel sources. I do use the vanilla kernel because at one point I
> > needed features from a version that wasn't yet on portage.
> >
> 
> How long ago was this?  It looks like gentoo-sources just tracks the
> stable kernel, and so does vanilla-sources.  If you want mainline you
> need git-sources, assuming you aren't just pulling them from git
> yourself (an option you of-course have with vanilla too).
> 
> The config items in the gentoo-sources are really just master switches
> to turn on everything needed by openrc/systemd/etc - they're
> conveniences just like meta-packages in portage.
> 
> Now, gentoo-sources DOES include additional patches, and some of them
> are features.  It is of course entirely possible that they could cause
> problems, but I imagine that they're selected fairly carefully.
> 
> The general philosophy mixed with some very dated info can be found at:
> http://dev.gentoo.org/~mpagano/genpatches/
> 
> --
> Rich
> 

Not that long ago maybe 2-3 months, it may be very close behind upstream but 
at that time it was. 

It is the master switch that still causes the USB problem for me. I don't know 
exactly how that works but none of the usb serial drivers in the kernel have 
my device id hardcoded on the devices table, if I add it to some of the 
drivers and recompile they get detected but work only if I use file IO system 
calls to communicate with it. If I just disable the gentoo master switches it 
works out of the box with any application. Everything else that I need works 
fine with the switch disabled.
 
----------
Fernando Rodriguez
frodriguez.developer@outlook.com


      reply	other threads:[~2014-10-29 20:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18  4:17 [gentoo-user] kernel 3.17.0 Philip Webb
2014-10-18  4:38 ` Tomas Mozes
2014-10-18 11:33 ` Alan McKinnon
2014-10-18 21:09   ` Stefan G. Weichinger
2014-10-18 21:59     ` Alan McKinnon
2014-10-18 21:16 ` Volker Armin Hemmann
2014-10-20  5:06   ` Tomas Mozes
2014-10-23 14:15     ` Andrew Savchenko
2014-10-24 13:59     ` Volker Armin Hemmann
2014-10-20  8:59   ` Michael Mattes
2014-10-24  3:53     ` Fernando Rodriguez
2014-10-24 11:22       ` Rich Freeman
2014-10-29 20:22         ` Fernando Rodriguez [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=BLU437-SMTP410EC6A99298E0DDDAD898D9C0@phx.gbl \
    --to=frodriguez.developer@outlook.com \
    --cc=gentoo-user@lists.gentoo.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