oun...@lists.openembedded.org
> > > [mailto:openembedded-core-boun...@lists.openembedded.org] On
> Behalf
> > > Of Khem Raj
> > > Sent: Wednesday, February 15, 2017 5:17 PM
> > > To: openembedded-core@lists.openembedded.org
> > > Subject: Re: [OE-core] Suggeste
Wednesday, February 15, 2017 5:17 PM
> > To: openembedded-core@lists.openembedded.org
> > Subject: Re: [OE-core] Suggested RREPLACES/RCONFLICTS for easier kernel-
> > image upgrades
> >
> >
> >
> > On 2/15/17 1:54 PM, Bryan Evenson wrote:
> > > For
Subject: Re: [OE-core] Suggested RREPLACES/RCONFLICTS for easier kernel-
> image upgrades
>
>
>
> On 2/15/17 1:54 PM, Bryan Evenson wrote:
> > For one project I'm using an Atmel AT91SAM9G25 processor, and I started
> when support for the chip wasn't fully integrat
On Thu, Feb 16, 2017 at 5:43 AM, Bryan Evenson wrote:
>
> I tried that and it didn't make a difference; without the specific previous
> package names listed in RDEPENDS/RCONFLICTS, opkg does not recognize the new
> kernel-image as an upgrade. From my understanding PE only affects the
> version
On 2/15/17 1:54 PM, Bryan Evenson wrote:
> For one project I'm using an Atmel AT91SAM9G25 processor, and I started when
> support for the chip wasn't fully integrated into the mainline kernel. As a
> result, I was using Atmel's Linux fork. Support has been in the mainline
> kernel for a whil
For one project I'm using an Atmel AT91SAM9G25 processor, and I started when
support for the chip wasn't fully integrated into the mainline kernel. As a
result, I was using Atmel's Linux fork. Support has been in the mainline
kernel for a while now, so in the middle of doing other updates I pl
