On Thu, Nov 06, 2014 at 02:02:49AM +, Masao Uebayashi wrote:
> Module Name: src
> Committed By: uebayasi
> Date: Thu Nov 6 02:02:49 UTC 2014
>
> Modified Files:
> src: build.sh
>
> Log Message:
> build.sh: New operation "kernels" to build all kernels
Documentation update?
Jo
> On Nov 5, 2014, at 6:09 PM, Masao Uebayashi wrote:
>
> On Thu, Nov 6, 2014 at 4:03 AM, Taylor R Campbell
> wrote:
>> Why use a string-keyed table with run-time lookups instead of a C
>> object with a C declaration?
>>
>> /* ioconf.h */
>> extern struct cfiattrdata xxxbus;
>>
>> /* xxx.c */
Builders will surely be happy to see how the output of "build.sh -m
evbearmv7-el kernels" looks like. :)
On Thu, Nov 6, 2014 at 4:03 AM, Taylor R Campbell
wrote:
> Why use a string-keyed table with run-time lookups instead of a C
> object with a C declaration?
>
> /* ioconf.h */
> extern struct cfiattrdata xxxbus;
>
> /* xxx.c */
> config_found(self, &xxxbus);
I tend to prefer indirect looku
Date: Thu, 6 Nov 2014 01:54:12 +0900
From: Masao Uebayashi
For future reference:
I think any "xxxbus" interface attribute (aka bus) should provide
xxxbusprint (and xxxbussubmatch if multiple children). I'll probably
change config(1) to extend cfiattrdata like:
struct cfiat
On Thu, Nov 6, 2014 at 1:54 AM, Masao Uebayashi wrote:
> struct cfiattrdata {
> const char *ci_name;
> cfprint_t ci_print;
> cfsubmatch_t ci_submatch;
> int ci_loclen;
> const struct cflocdesc ci_locdesc[];
> };
Actually, ci_name, ci_print, ci_submatch are
For future reference:
I think any "xxxbus" interface attribute (aka bus) should provide
xxxbusprint (and xxxbussubmatch if multiple children). I'll probably
change config(1) to extend cfiattrdata like:
struct cfiattrdata {
const char *ci_name;
cfprint_t ci_print;
cfsubmat
