Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[Russell Senior]

> "David" == David Woodhouse  writes:

David> On Wed, 2017-02-15 at 14:03 -0800, Russell Senior wrote:
>> 
>> I just tried r3499 (master branch), and it works too,

David> Nice. Do you want to reinstate the default configuration for it,
David> which was removed in commit 9e0759ea2? See how I've just done it
David> for Geos.  Wha t is in /tmp/sysinfo/board_name?

There is no /tmp/sysinfo on my test alix.  Furthermore, it seems to be
populated from target/linux/x86/base-files/lib/preinit/20_sysinfo, which
asks files in /sys/devices/virtual/dmi/id/, but my alix doesn't have a
/sys/devices/virtual/dmi, either, which probably explains the former.

David> You can configure the baud rate in the Alix2 BIOS, can't you?

I suppose I could, but I have 20-odd of these in the field, which makes
that route a bit tedious.  Or I could override it in my build .config
stub.


-- 
Russell Senior, President
russ...@personaltelco.net

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[David Woodhouse]

On Wed, 2017-02-15 at 14:03 -0800, Russell Senior wrote:
> 
> I just tried r3499 (master branch), and it works too, 

Nice. Do you want to reinstate the default configuration for it, which
was removed in commit 9e0759ea2? See how I've just done it for Geos.
Wha
t is in /tmp/sysinfo/board_name?

You can configure the baud rate in the Alix2 BIOS, can't you?

> although I do see this stack trace during boot:

Yeah, I saw that. Was ignoring it for now. 

smime.p7s
Description: S/MIME cryptographic signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[Russell Senior]

> "Russell" == Russell Senior  writes:

> "Russell" == Russell Senior  writes:
> "David" == David Woodhouse  writes:
David> On Wed, 2017-02-15 at 12:52 -0800, Russell Senior wrote:
 I last built on February 1, circa r3226, and that works.

David> But not with an out-of-the-box configuration anyway, right?

Russell> Pretty much.  This was my .config stub:

Russell> CONFIG_TARGET_x86=y CONFIG_TARGET_x86_geode=y CONFIG_DEVEL=y
Russell> CONFIG_BUILD_LOG=y

Also, tried 17.01-SNAPSHOT, r3180-dbb8e04472

it "works" too, afaict.  No stack trace, which I assume is related to
the 4.9.x kernel in master, somehow.


-- 
Russell Senior, President
russ...@personaltelco.net

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[Russell Senior]

> "Russell" == Russell Senior  writes:

> "David" == David Woodhouse  writes:
David> On Wed, 2017-02-15 at 12:52 -0800, Russell Senior wrote:
>>> I last built on February 1, circa r3226, and that works.

David> But not with an out-of-the-box configuration anyway, right?

Russell> Pretty much.  This was my .config stub:

Russell>  CONFIG_TARGET_x86=y CONFIG_TARGET_x86_geode=y CONFIG_DEVEL=y
Russell> CONFIG_BUILD_LOG=y

I just tried r3499 (master branch), and it works too, although I do see
this stack trace during boot:

[...]
[   10.578574] kmodloader: loading kernel modules from /etc/modules.d/*
[   10.600627] [ cut here ]
[   10.614641] WARNING: CPU: 0 PID: 674 at drivers/base/dd.c:344 
driver_probe_device+0x58/0x1a5
[   10.640008] Modules linked in: geode_aes(+) cbc button_hotplug aead 
cryptomgr crypto_null
[   10.665186] CPU: 0 PID: 674 Comm: kmodloader Not tainted 4.9.8 #0
[   10.683549]   c102aed4 0158 0009 cf8d1064 d0884794 0001 
d0884794
[   10.707317]  c102af54 0009   c11988e7 cf8d1064 d0884794 
cf8d1098
[   10.731207]  c13f5a00 c1198a89  d0884794  c11977f3 cf81ea0c 
cf9077b0
[   10.755074] Call Trace:
[   10.762538]  [] ? __warn+0xa9/0xc0
[   10.775470]  [] ? warn_slowpath_null+0xf/0x13
[   10.791246]  [] ? driver_probe_device+0x58/0x1a5
[   10.807742]  [] ? __driver_attach+0x55/0x70
[   10.823014]  [] ? bus_for_each_dev+0x47/0x63
[   10.838547]  [] ? driver_attach+0x11/0x13
[   10.853314]  [] ? driver_probe_device+0x1a5/0x1a5
[   10.870084]  [] ? bus_add_driver+0xa7/0x17f
[   10.885353]  [] ? 0xd0886000
[   10.896710]  [] ? driver_register+0x6c/0x9d
[   10.911921]  [] ? do_one_initcall+0x85/0x110
[   10.927447]  [] ? call_usermodehelper_exec+0xc5/0xd0
[   10.945058]  [] ? free_vmap_area_noflush+0x26/0x63
[   10.962170]  [] ? kmem_cache_alloc+0x58/0x7c
[   10.977650]  [] ? do_init_module+0x42/0x18d
[   10.992925]  [] ? load_module+0x12a1/0x161f
[   11.008186]  [] ? SyS_init_module+0x8c/0xa3
[   11.023392]  [] ? do_fast_syscall_32+0x83/0xe1
[   11.039475]  [] ? sysenter_past_esp+0x47/0x75
[   11.055232] ---[ end trace fd70a030d2f480e5 ]---
[   11.069901] Geode LX AES :00:01.2: GEODE AES engine enabled.
[...]


-- 
Russell Senior, President
russ...@personaltelco.net

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[Russell Senior]

> "David" == David Woodhouse  writes:

David> On Wed, 2017-02-15 at 12:52 -0800, Russell Senior wrote:
>> I last built on February 1, circa r3226, and that works.

David> But not with an out-of-the-box configuration anyway, right?

Pretty much.  This was my .config stub:

 CONFIG_TARGET_x86=y
 CONFIG_TARGET_x86_geode=y
 CONFIG_DEVEL=y
 CONFIG_BUILD_LOG=y


-- 
Russell Senior, President
russ...@personaltelco.net

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[David Woodhouse]

On Wed, 2017-02-15 at 12:52 -0800, Russell Senior wrote:
> I last built on February 1, circa r3226, and that works.

But not with an out-of-the-box configuration anyway, right?


smime.p7s
Description: S/MIME cryptographic signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[Russell Senior]

> "David" == David Woodhouse  writes:

David> On Wed, 2017-02-15 at 12:24 -0800, Russell Senior wrote:
>> 
>> 
David> In the same PR#840:
>> 
David> b5bec324fb6eecc483e093a231d7d3fc050bf344 x86: Set default baud
David> rate on Geode images to 115200
>> 
>> The alix2 (also a Geode) uses 38400 in the BIOS.

David> Hm. The Geos uses 115200 in the BIOS. Does the alix2 actually
David> work? 

David> It looks like via-rhine Ethernet support was dropped when the
David> Geode subtargets were merged, and never added back again until I
David> did it today. Which means that the default images won't work for
David> alix2 anyway, right? They do for Geos...

I last built on February 1, circa r3226, and that works.

David> The three Geode-based targets that got merged all had *different*
David> default baud rates. We just need to pick one, and picking the one
David> that's default on most boards, most useful, and matches the board
David> that is actively (if sporadically) being maintained does seem
David> like it's not the worst idea...

I've only ever seen the alix, so I'm biased. ;-)


-- 
Russell Senior, President
russ...@personaltelco.net

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[David Woodhouse]

On Wed, 2017-02-15 at 12:24 -0800, Russell Senior wrote:
> 
> 
> David> In the same PR#840:
> 
> David> b5bec324fb6eecc483e093a231d7d3fc050bf344 x86: Set default baud
> David> rate on Geode images to 115200
> 
> The alix2 (also a Geode) uses 38400 in the BIOS.

Hm. The Geos uses 115200 in the BIOS. Does the alix2 actually work? 

It looks like via-rhine Ethernet support was dropped when the Geode
subtargets were merged, and never added back again until I did it
today. Which means that the default images won't work for alix2 anyway,
right? They do for Geos...

The three Geode-based targets that got merged all had *different*
default baud rates. We just need to pick one, and picking the one
that's default on most boards, most useful, and matches the board that
is actively (if sporadically) being maintained does seem like it's not
the worst idea...



smime.p7s
Description: S/MIME cryptographic signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[Russell Senior]

> "David" == David Woodhouse  writes:

David> On Wed, 2017-02-15 at 17:14 +, David Woodhouse wrote:

>> I'd like to change the default serial baud rate to 115200 too... will
>> do that shortly.

David> In the same PR#840:

David> b5bec324fb6eecc483e093a231d7d3fc050bf344 x86: Set default baud
David> rate on Geode images to 115200

The alix2 (also a Geode) uses 38400 in the BIOS.


-- 
Russell Senior, President
russ...@personaltelco.net

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[Alberto Bursi]

On 02/15/2017 05:45 PM, Jo-Philipp Wich wrote:
> Hi,
>
> To get final fixes into the release please mention Git commits you like
> to see cherry-picked in to lede-17.01  until Sunday, the 19th.
>

a9d347c11c34e48d17e1a4902a56d1f2f577bfab
uboot-kirkwood: fix goflexhome/net bootcommand

-Alberto

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[David Woodhouse]

On Wed, 2017-02-15 at 17:14 +, David Woodhouse wrote:
> On Wed, 2017-02-15 at 17:45 +0100, Jo-Philipp Wich wrote:
> > 
> > 
> > To get final fixes into the release please mention Git commits you like
> > to see cherry-picked in to lede-17.01  until Sunday, the 19th.
> 657418db68fe2be89bdba2a147a08168d7a760ba x86: Add configuration back for 
> Traverse Geos
> 27a635f0b487eb54bde58639c80080396bbf1c03 x86: Move Traverse Geos configs into 
> x86 base-files
> add465f1be5d092ef049306ea2a211ff3f82b146 x86: Enable DIAG LED on Geos
> 9a6c9325564439e0c9bb3209931787a492fa8f9b x86: Add board configs for the PC 
> Engines APU2
> 501c2a626533feaec67b54d367fe51ea5cfec699 x86: Add Geos profile for Geode 
> subtarget
> 
> The last one is from https://github.com/lede-project/source/pull/840
> 
> I'd like to change the default serial baud rate to 115200 too... will do that 
> shortly.

In the same PR#840: 

b5bec324fb6eecc483e093a231d7d3fc050bf344 x86: Set default baud rate on Geode 
images to 115200


smime.p7s
Description: S/MIME cryptographic signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] LEDE v17.01.0 schedule adjusted

[David Woodhouse]

On Wed, 2017-02-15 at 17:45 +0100, Jo-Philipp Wich wrote:
> 
> To get final fixes into the release please mention Git commits you like
> to see cherry-picked in to lede-17.01  until Sunday, the 19th.

657418db68fe2be89bdba2a147a08168d7a760ba x86: Add configuration back for 
Traverse Geos
27a635f0b487eb54bde58639c80080396bbf1c03 x86: Move Traverse Geos configs into 
x86 base-files
add465f1be5d092ef049306ea2a211ff3f82b146 x86: Enable DIAG LED on Geos
9a6c9325564439e0c9bb3209931787a492fa8f9b x86: Add board configs for the PC 
Engines APU2
501c2a626533feaec67b54d367fe51ea5cfec699 x86: Add Geos profile for Geode 
subtarget

The last one is from https://github.com/lede-project/source/pull/840

I'd like to change the default serial baud rate to 115200 too... will do that 
shortly.

smime.p7s
Description: S/MIME cryptographic signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] LEDE v17.01.0 schedule adjusted

[Jo-Philipp Wich]

Hi,

due to ongoing bug fixing efforts and some outstanding work on solving
regressions I'd like to postpone the release of 17.01.0 final by a week.

According to the revised plan, I'd like to tag v17.01.0 on Monday, the
20th and release final binary images on Wednesday, the 22th.

--

To get final fixes into the release please mention Git commits you like
to see cherry-picked in to lede-17.01  until Sunday, the 19th.

Also please mention known broken targets or images that should get
disabled for the release in case there is no readily available fixes
available.

--

Once we pushed 17.01.0 final, the lede-17.01 branch will be open for
device support changes and larger non-bugfix commits again with the goal
to prepare v17.01.1 until the end of March 2017.

The LEDE 17.01 builders will continue processing the external package
feeds as usual so updated packages will continue to be available.


I'd like to thank our contributors very much for the outstanding work
being done to make this release possible!


Bye,
Jo

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev