On 19 March 2018 at 23:00, Giordon Stark wrote:
> Comments inline.
>
> On Mon, Mar 19, 2018 at 4:18 AM Nathan Rossi wrote:
>>
>> On 19 March 2018 at 01:42, Giordon Stark wrote:
>> > Hi Nathan,
>> >
>> > On Sun, Mar 18, 2018 at 6:29 AM Nathan Rossi
>> > wrote:
>> >>
>> >> On 18 March 2018 at 04:
Comments inline.
On Mon, Mar 19, 2018 at 4:18 AM Nathan Rossi wrote:
> On 19 March 2018 at 01:42, Giordon Stark wrote:
> > Hi Nathan,
> >
> > On Sun, Mar 18, 2018 at 6:29 AM Nathan Rossi
> wrote:
> >>
> >> On 18 March 2018 at 04:57, Giordon Stark wrote:
> >> > Hi,
> >> >
> >> > Based on Jorge
On 19 March 2018 at 01:42, Giordon Stark wrote:
> Hi Nathan,
>
> On Sun, Mar 18, 2018 at 6:29 AM Nathan Rossi wrote:
>>
>> On 18 March 2018 at 04:57, Giordon Stark wrote:
>> > Hi,
>> >
>> > Based on Jorge's suggestion (cc'd), I uncommented my lines in
>> > device-tree.bbappend to set compatible
Hi Nathan,
On Sun, Mar 18, 2018 at 6:29 AM Nathan Rossi wrote:
> On 18 March 2018 at 04:57, Giordon Stark wrote:
> > Hi,
> >
> > Based on Jorge's suggestion (cc'd), I uncommented my lines in
> > device-tree.bbappend to set compatible machine = ".*" for my particular
> > boards as it is being do
On 18 March 2018 at 04:57, Giordon Stark wrote:
> Hi,
>
> Based on Jorge's suggestion (cc'd), I uncommented my lines in
> device-tree.bbappend to set compatible machine = ".*" for my particular
> boards as it is being done upstream... and bitbake seems to be happier with
> that, but then I run int
Hi,
Based on Jorge's suggestion (cc'd), I uncommented my lines in
device-tree.bbappend to set compatible machine = ".*" for my particular
boards as it is being done upstream... and bitbake seems to be happier with
that, but then I run into this error
ERROR: Nothing PROVIDES 'virtual/xilinx-platfo
Hi,
I've been trying to understand/figure out what changed to break something
that was definitely working on pyro -- but it's been hard to trace changes
because of the move/restructuring...
When I re-run bitbake for an image that I've built in pyro just fine using
all the same code, I see this er