- User Since
- Oct 2 2015, 1:17 PM (145 w, 3 d)
Sat, Jul 14
Thu, Jul 12
Wed, Jul 11
Tue, Jul 10
Seems reasonable...hurray for de-duplication.
Sun, Jul 8
A-ha! \0/ This is the solution I was searching for.
Fri, Jul 6
Thu, Jul 5
Mon, Jul 2
Thu, Jun 28
Wed, Jun 27
I guess what I'm getting at is- if it's not commonly set or exposed, I think we should go ahead and do this. If we get it wrong, there's always the temporary workaround of env LC_CTYPE=C ifconfig and exposing the SSID Encoding bit doesn't appear to be a monumental task.
Tue, Jun 26
Some relatively minor issues:
- The logic for static_env.disabled was backwards
- Initializing the dynamic env now uses the first value for a variable that it finds, and any later assignments of the same value are ignored. This is to match how searching the static environment in the kernel works so that we get consistent results between the static environment and the dynamic environment. config(8) should setup the static environment for us in such a way that a later assignment to a variable overrides an earlier assignment.
- In rS273487. @cperciva started zero'ing out the static environment as it filled the dynamic environment to avoid leaking data from the kernel environment. I've extended this cleaning to zero out even the skipped entries to eradicate all traces of the static environment once we've provisioned the dynamic one.
Mon, Jun 25
Avoid reallocation if we're looking at a same-size replacement.
Add realloc missed in previous revision
I intend to commit this by the end of next week (July 6-8 time frame) without any strong objections, given the lack of any outcry from my e-mail to -arch/-embedded.
Sat, Jun 23
This idea courtesy of ian@:
Fri, Jun 22
Updated following discussion on IRC with Ian:
Add back in the ability to specify static_env.disabled and static_hints.disabled. The reimplementation of these follows suit with how we treat environments in the new age- static_hints.disabled may be specified in either static_env or loader(8) env, and static_env.disabled may only be specified in loader(8) env.
Thu, Jun 21
Tested on: Lamobo R1 w/ root-on-SD
Wed, Jun 20
Tue, Jun 19
Please do mention in the commit message that MMCCAM is not usable on Allwinner boards using root-on-MMC to curtail that set of complaints if people actually try it.