Am 14.08.2014 23:35, schrieb Stephen Warren:
On 08/14/2014 02:53 PM, Tom Rini wrote:
On Thu, Aug 14, 2014 at 01:50:31PM -0600, Stephen Warren wrote:
[snip]
uenv.txt is the opposite; it's very U-Boot specific, and more about
internal implementation details of U-Boot. In particular, I only see
a
On 08/14/2014 02:53 PM, Tom Rini wrote:
On Thu, Aug 14, 2014 at 01:50:31PM -0600, Stephen Warren wrote:
[snip]
uenv.txt is the opposite; it's very U-Boot specific, and more about
internal implementation details of U-Boot. In particular, I only see
a use-case for uenv.txt on systems that have no
Am 14.08.2014 22:53, schrieb Tom Rini:
On Thu, Aug 14, 2014 at 01:50:31PM -0600, Stephen Warren wrote:
[snip]
uenv.txt is the opposite; it's very U-Boot specific, and more about
internal implementation details of U-Boot. In particular, I only see
a use-case for uenv.txt on systems that have now
On Thu, Aug 14, 2014 at 01:50:31PM -0600, Stephen Warren wrote:
[snip]
> uenv.txt is the opposite; it's very U-Boot specific, and more about
> internal implementation details of U-Boot. In particular, I only see
> a use-case for uenv.txt on systems that have nowhere to store the
> U-Boot environme
Am 14.08.2014 22:08, schrieb Stephen Warren:
On 08/14/2014 01:59 PM, Alexander Holler wrote:
Am 14.08.2014 21:51, schrieb Stephen Warren:
On 08/14/2014 01:38 PM, Alexander Holler wrote:
Am 14.08.2014 17:49, schrieb Stephen Warren:
On 08/14/2014 02:25 AM, Alexander Holler wrote:
As I've jus
On 08/14/2014 01:59 PM, Alexander Holler wrote:
Am 14.08.2014 21:51, schrieb Stephen Warren:
On 08/14/2014 01:38 PM, Alexander Holler wrote:
Am 14.08.2014 17:49, schrieb Stephen Warren:
On 08/14/2014 02:25 AM, Alexander Holler wrote:
As I've just remembered where I did see your name before,
Am 14.08.2014 21:51, schrieb Stephen Warren:
On 08/14/2014 01:38 PM, Alexander Holler wrote:
Am 14.08.2014 17:49, schrieb Stephen Warren:
On 08/14/2014 02:25 AM, Alexander Holler wrote:
As I've just remembered where I did see your name before, the config
for
the rpi (as found in 2004.04) mis
On 08/14/2014 01:38 PM, Alexander Holler wrote:
Am 14.08.2014 17:49, schrieb Stephen Warren:
On 08/14/2014 02:25 AM, Alexander Holler wrote:
As I've just remembered where I did see your name before, the config for
the rpi (as found in 2004.04) misses the uenvcmd. That's necessary to
execute c
On 08/14/2014 12:41 PM, Robert Nelson wrote:
On Thu, Aug 14, 2014 at 10:49 AM, Stephen Warren wrote:
On 08/14/2014 02:25 AM, Alexander Holler wrote:
Am 31.07.2014 21:57, schrieb Stephen Warren:
Huh, I do see that now. I must have been looking at the content of
common/cmd_nvedit.c from the w
Am 14.08.2014 17:49, schrieb Stephen Warren:
On 08/14/2014 02:25 AM, Alexander Holler wrote:
As I've just remembered where I did see your name before, the config for
the rpi (as found in 2004.04) misses the uenvcmd. That's necessary to
execute commands when using uEnv.txt.
It's easily done wi
On Thu, Aug 14, 2014 at 01:41:16PM -0500, Robert Nelson wrote:
> On Thu, Aug 14, 2014 at 10:49 AM, Stephen Warren
> wrote:
> > On 08/14/2014 02:25 AM, Alexander Holler wrote:
> >>
> >> Am 31.07.2014 21:57, schrieb Stephen Warren:
> >>
> >>> Huh, I do see that now. I must have been looking at the
On Thu, Aug 14, 2014 at 10:49 AM, Stephen Warren wrote:
> On 08/14/2014 02:25 AM, Alexander Holler wrote:
>>
>> Am 31.07.2014 21:57, schrieb Stephen Warren:
>>
>>> Huh, I do see that now. I must have been looking at the content of
>>> common/cmd_nvedit.c from the wrong branch, which didn't include
On 08/14/2014 02:25 AM, Alexander Holler wrote:
Am 31.07.2014 21:57, schrieb Stephen Warren:
Huh, I do see that now. I must have been looking at the content of
common/cmd_nvedit.c from the wrong branch, which didn't include that
patch. I could have sworn I checked git history too, but evidently
Am 31.07.2014 21:57, schrieb Stephen Warren:
Huh, I do see that now. I must have been looking at the content of
common/cmd_nvedit.c from the wrong branch, which didn't include that
patch. I could have sworn I checked git history too, but evidently not.
It is indeed clearly there right before the
Am 06.08.2014 13:18, schrieb Alexander Holler:
Am 06.08.2014 12:44, schrieb Måns Rullgård:
Alexander Holler writes:
Am 06.08.2014 08:43, schrieb Wolfgang Denk:
Dear Alexander,
In message <53dfdc99.2020...@ahsoftware.de> you wrote:
At least I've understood it such that nobody still has an
Am 06.08.2014 12:44, schrieb Måns Rullgård:
Alexander Holler writes:
Am 06.08.2014 08:43, schrieb Wolfgang Denk:
Dear Alexander,
In message <53dfdc99.2020...@ahsoftware.de> you wrote:
At least I've understood it such that nobody still has an objection=20
against the new feature for "env im
Alexander Holler writes:
> Am 06.08.2014 08:43, schrieb Wolfgang Denk:
>> Dear Alexander,
>>
>> In message <53dfdc99.2020...@ahsoftware.de> you wrote:
>>>
>>> At least I've understood it such that nobody still has an objection=20
>>> against the new feature for "env import -t" (-r).
>>
>> I objec
Am 06.08.2014 12:02, schrieb Alexander Holler:
Am 06.08.2014 08:43, schrieb Wolfgang Denk:
Dear Alexander,
In message <53dfdc99.2020...@ahsoftware.de> you wrote:
At least I've understood it such that nobody still has an objection=20
against the new feature for "env import -t" (-r).
I object
Am 06.08.2014 08:43, schrieb Wolfgang Denk:
Dear Alexander,
In message <53dfdc99.2020...@ahsoftware.de> you wrote:
At least I've understood it such that nobody still has an objection=20
against the new feature for "env import -t" (-r).
I object if it would be added without maintaining symmet
Dear Alexander,
In message <53dfdc99.2020...@ahsoftware.de> you wrote:
>
> At least I've understood it such that nobody still has an objection=20
> against the new feature for "env import -t" (-r).
I object if it would be added without maintaining symmetry with "env
export".
Best regards,
Wolf
Am 04.08.2014 12:00, schrieb Måns Rullgård:
Alexander Holler writes:
Why not just make "env import" treat \r like any other whitespace? It
would be a slight change from current behaviour, but the chance that
someone actually relies on a trailing \r being part of the value is
vanishingly smal
Alexander Holler writes:
> Am 03.08.2014 19:51, schrieb Wolfgang Denk:
>> Dear Alexander,
>>
>> In message <53de658f.5010...@ahsoftware.de> you wrote:
>>>
>>> Just to clarify: I see uEnv.txt (which only was possible through your
>>> env import implementation) as a read-only configuration file for
Am 04.08.2014 08:47, schrieb Alexander Holler:
But it would not be really symmetric. The -r for "env import" makes "env
import" eat both formats, which means it can be used almost always, but
using -r with "env export" would be a decision which always would be
wrong for many people.
Of course,
Am 03.08.2014 19:51, schrieb Wolfgang Denk:
Dear Alexander,
In message <53de658f.5010...@ahsoftware.de> you wrote:
Just to clarify: I see uEnv.txt (which only was possible through your
env import implementation) as a read-only configuration file for u-boot,
This is just one of the many possi
Dear Alexander,
In message <53de658f.5010...@ahsoftware.de> you wrote:
>
> Just to clarify: I see uEnv.txt (which only was possible through your
> env import implementation) as a read-only configuration file for u-boot,
This is just one of the many possible usages.
> And I don't think all the
Dear Alexander,
In message <53dd53a5.3010...@ahsoftware.de> you wrote:
>
> > Should we not, for reasons of symmetry, then also extend "env export"
> > by such a "-r" option?
>
> Sorry, but I don't follow the new features of u-boot that closely.
This is not a new feature.
> Is it already possibl
Am 02.08.2014 23:09, schrieb Alexander Holler:
Am 01.08.2014 14:08, schrieb Wolfgang Denk:
Should we not, for reasons of symmetry, then also extend "env export"
by such a "-r" option?
Sorry, but I don't follow the new features of u-boot that closely.
Is it already possible to save an export
Am 01.08.2014 14:08, schrieb Wolfgang Denk:
Dear Alexander Holler,
In message <1405352998-7707-2-git-send-email-hol...@ahsoftware.de> you wrote:
When this option is enabled, CRLF is treated like LF when importing environments
from text files, which means CRs ('\r') in front of LFs ('\n') are ju
Dear Alexander Holler,
In message <1405352998-7707-2-git-send-email-hol...@ahsoftware.de> you wrote:
> When this option is enabled, CRLF is treated like LF when importing
> environments
> from text files, which means CRs ('\r') in front of LFs ('\n') are just
> ignored.
>
> Drawback of enabling
On 07/31/2014 01:51 PM, Tom Rini wrote:
On Wed, Jul 30, 2014 at 04:47:57PM -0600, Stephen Warren wrote:
On 07/14/2014 09:49 AM, Alexander Holler wrote:
When this option is enabled, CRLF is treated like LF when importing environments
>from text files, which means CRs ('\r') in front of LFs ('\
On Wed, Jul 30, 2014 at 04:47:57PM -0600, Stephen Warren wrote:
> On 07/14/2014 09:49 AM, Alexander Holler wrote:
> >When this option is enabled, CRLF is treated like LF when importing
> >environments
> >from text files, which means CRs ('\r') in front of LFs ('\n') are just
> >ignored.
> >
> >D
On 07/14/2014 09:49 AM, Alexander Holler wrote:
When this option is enabled, CRLF is treated like LF when importing environments
from text files, which means CRs ('\r') in front of LFs ('\n') are just ignored.
Drawback of enabling this option is that (maybe exported) variables which have
a trail
When this option is enabled, CRLF is treated like LF when importing environments
from text files, which means CRs ('\r') in front of LFs ('\n') are just ignored.
Drawback of enabling this option is that (maybe exported) variables which have
a trailing CR in their content will get imported without
33 matches
Mail list logo