Re: [U-Boot] Apparent conflict between CONFIG_BLK and CONFIG_API

2017-04-08 Thread Tom Rini
On Tue, Mar 07, 2017 at 10:53:17PM +0100, f...@fuz.su wrote: > Good evening, > > I am trying to port FreeBSD to the ASUS Tinker Board, a computer based > on the Rockchip 3288 SoC. FreeBSD's boot loader (named loader(8)) needs > CONFIG_API to be enabled, but trying to build an U-Boot from trunk wi

Re: [U-Boot] Apparent conflict between CONFIG_BLK and CONFIG_API

2017-03-13 Thread Simon Glass
Hi Robert, On 13 March 2017 at 07:51, wrote: > Hello Simon, > > CONFIG_BLK is set by default for all Rockchip boards. Turning it off was > the first thing I tried, but I actually wasn't able to figure out how to > turn it off at all and was then advised elsewhere that this is probably > not a go

Re: [U-Boot] Apparent conflict between CONFIG_BLK and CONFIG_API

2017-03-13 Thread fuz
Hello Simon, CONFIG_BLK is set by default for all Rockchip boards. Turning it off was the first thing I tried, but I actually wasn't able to figure out how to turn it off at all and was then advised elsewhere that this is probably not a good idea either. Yours, Robert Clausecker On Mon, Mar 13,

Re: [U-Boot] Apparent conflict between CONFIG_BLK and CONFIG_API

2017-03-13 Thread Simon Glass
Hi, On 7 March 2017 at 14:53, wrote: > Good evening, > > I am trying to port FreeBSD to the ASUS Tinker Board, a computer based > on the Rockchip 3288 SoC. FreeBSD's boot loader (named loader(8)) needs > CONFIG_API to be enabled, but trying to build an U-Boot from trunk with > both CONFIG_API an

[U-Boot] Apparent conflict between CONFIG_BLK and CONFIG_API

2017-03-08 Thread fuz
Good evening, I am trying to port FreeBSD to the ASUS Tinker Board, a computer based on the Rockchip 3288 SoC. FreeBSD's boot loader (named loader(8)) needs CONFIG_API to be enabled, but trying to build an U-Boot from trunk with both CONFIG_API and CONFIG_BLK (as required for Rockchip SoC's?) lead