[linux-yocto] [PATCH] meta: add genericx86 BSP
Kamble, Nitin A
nitin.a.kamble at intel.com
Fri Sep 13 10:06:48 PDT 2013
> -----Original Message-----
> From: linux-yocto-bounces at yoctoproject.org [mailto:linux-yocto-
> bounces at yoctoproject.org] On Behalf Of Bruce Ashfield
> Sent: Friday, September 13, 2013 9:56 AM
> To: Development list for the linux-yocto*.git Linux kernel repositories
> Subject: Re: [linux-yocto] [PATCH] meta: add genericx86 BSP
>
> On 13-09-13 12:03 PM, Darren Hart wrote:
> > This is not being added, we're using common-pc. What is pending is my
> > update to the common-pc and common-pc-64 BSPs which Paul G. provided
> > some feedback for and I updated the branch which is ready to be pulled
> > here:
> >
> > git://git.yoctoproject.org/linux-yocto-contrib dvhart/3.10/meta
> > http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=dvhart
> > /3.10/meta
> >
> > This should be all that is outstanding for genericx86/common-pc in
> > linux-yocto currently.
>
> Aha. My misunderstanding, it got a bit muddy in the middle. As you can see
> in your inbox, I've merged these, pushed them out and sent the pull request
> for the SRCREV update.
Darren,
Does this impact other BSPs? Or in other words does this demand srcrev updates for other BSPs?
Thanks,
Nitin
>
> Bruce
>
> >
> > --
> > Darren
> >
> > On Fri, 2013-09-13 at 09:12 -0400, Bruce Ashfield wrote:
> >> ping again.
> >>
> >> I still haven't seen an updated, an reposted merge of this with common-
> pc.
> >> Did my mail client manage to drop it ?
> >>
> >> Bruce
> >>
> >> On Mon, Sep 9, 2013 at 2:06 PM, Bruce Ashfield
> <bruce.ashfield at gmail.com> wrote:
> >>> On Wed, Aug 21, 2013 at 4:17 PM, Bruce Ashfield
> >>> <bruce.ashfield at windriver.com> wrote:
> >>>> On 13-08-21 01:33 PM, Darren Hart wrote:
> >>>>>
> >>>>> On Wed, 2013-08-21 at 17:57 +0100, Ross Burton wrote:
> >>>>>>
> >>>>>> This BSP aims at supporting a broad range of Intel platforms,
> >>>>>> from Atom up to Xeon. As such the kernel includes a range of
> >>>>>> drivers, and the corresponding machine configuration in
> >>>>>> meta-yocto-bsp includes a range of user-space drivers.
> >>>>>>
> >>>>>> Signed-off-by: Ross Burton <ross.burton at intel.com>
> >>>>>> ---
> >>>>>> .../bsp/genericx86/genericx86-standard.scc | 28
> >>>>>> ++++++++++++++++++++
> >>>>>> 1 file changed, 28 insertions(+)
> >>>>>> create mode 100644
> >>>>>> meta/cfg/kernel-cache/bsp/genericx86/genericx86-standard.scc
> >>>>>>
> >>>>>> diff --git
> >>>>>> a/meta/cfg/kernel-cache/bsp/genericx86/genericx86-standard.scc
> >>>>>> b/meta/cfg/kernel-cache/bsp/genericx86/genericx86-standard.scc
> >>>>>> new file mode 100644
> >>>>>> index 0000000..94d8ca7
> >>>>>> --- /dev/null
> >>>>>> +++ b/meta/cfg/kernel-cache/bsp/genericx86/genericx86-
> standard.sc
> >>>>>> +++ c
> >>>>>> @@ -0,0 +1,28 @@
> >>>>>> +define KMACHINE genericx86
> >>>>>> +define KTYPE standard
> >>>>>> +define KARCH i386
> >>>>>> +
> >>>>>> +# TODO: long-term move away from common-pc?
> >>>>>> +include bsp/common-pc/common-pc-standard.scc
> >>>>>> +branch atom-pc
> >>>>>> +
> >>>>>> +include cfg/x86.scc
> >>>>>> +include cfg/boot-live.scc
> >>>>>> +
> >>>>>> +include features/power/intel.scc
> >>>>>> +
> >>>>>> +# Ideally all of these below would be modules instead of built-in.
> >>>>>> +
> >>>>>> +# common-pc brings in the other USB controllers include
> >>>>>> +features/usb/xhci-hcd.scc
> >>>>>
> >>>>>
> >>>>> And should really bring this one in too...
> >>>>
> >>>>
> >>>> Agreed!
> >>>>
> >>>>
> >>>>>
> >>>>>> +
> >>>>>> +# Intel ethernet, old and new Intel wireless.
> >>>>>> +include features/rfkill/rfkill.scc include
> >>>>>> +features/intel-e1xxxx/intel-e1xxxx.scc
> >>>>>> +include features/iwlwifi/iwlwifi.scc include
> >>>>>> +features/iwlegacy/iwlegacy.scc
> >>>>>> +
> >>>>>> +# Intel Gen and GMA500. common-pc provides Vesa framebuffer.
> >>>>>> +include features/i915/i915.scc
> >>>>>> +include features/drm-gma500/drm-gma500.scc
> >>>>>> +include features/drm-gma500/drm-gma3600.scc
> >>>>>
> >>>>>
> >>>>> This is really a fairly small change. Any reason this shouldn't
> >>>>> just be an update to common-pc? Is there a conceptual difference
> here?
> >>>>
> >>>>
> >>>> I'd like to see them just merge. They are both targeting a similar
> >>>> set of commodity hardware platforms. Sure, qemux86 will pick these
> >>>> up as well, but as qemu gains more functionality we can use more
> >>>> and more of the options.
> >>>
> >>> ping. Did we collectively slip on this ? I was just trying to debug
> >>> a serial 8250 issue, and realized that none of the generic x86 parts
> >>> have merged.
> >>>
> >>> Bruce
> >>>
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Bruce
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> linux-yocto mailing list
> >>>> linux-yocto at yoctoproject.org
> >>>> https://lists.yoctoproject.org/listinfo/linux-yocto
> >>>
> >>>
> >>>
> >>> --
> >>> "Thou shalt not follow the NULL pointer, for chaos and madness await
> >>> thee at its end"
> >>
> >>
> >>
> >
>
> _______________________________________________
> linux-yocto mailing list
> linux-yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/linux-yocto
More information about the linux-yocto
mailing list