Nut/OS 4.9.6 Beta

[Ethernut]

... is available for download at
http://www.ethernut.de/en/download/

Changes can be viewed at
http://ethernut.svn.sourceforge.net/viewvc/ethernut?view=rev&revision=2702


Enjoy,

Harald Kipp
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[uprinz]

Hi!

If this equals the trunk, I am already at it :)
But my new key an led drivers arrived some minutes to late.

Best Regards, Ulrich

Ps: Thanks for the short support, it works!

Harald Kipp schrieb:

> ... is available for download at
> http://www.ethernut.de/en/download/
>
> Changes can be viewed at
> http://ethernut.svn.sourceforge.net/viewvc/ethernut?view=rev&revision=2702
>
>
> Enjoy,
>
> Harald Kipp
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[uprinz]

Hi!
 
Two problems:
Can it be, that the emac drivers are bound in different files, or the
dependencies to nutconf have changed to bind them correctly? If I update to
the latest trunk, I get compiler errors about not defined devEth0. Then I
see that there are quite several files having only small differences in
their names that define this devEth0... I'm a bit confused now.
If I do a fresh new checkout, the dependencies are correct and I can
compile the httd demo.
 
Second my two script files, previously located in nut/tools/scripts are
missing, so the arm-oocd burning option is no longer functioning.
Who threw them away and why?
 
Best regards, Ulrich
 
On Thu, 17 Sep 2009 16:29:16 +0200, Harald Kipp <harald.kipp@...>
wrote:
> ... is available for download at
> http://www.ethernut.de/en/download/ 
>  
> Changes can be viewed at
>
http://ethernut.svn.sourceforge.net/viewvc/ethernut?view=rev&revision=2702 
>  
>  
> Enjoy,
>  
> Harald Kipp
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Ethernut]

Ulrich Prinz wrote:

> Two problems:
> Can it be, that the emac drivers are bound in different files, or the
> dependencies to nutconf have changed to bind them correctly? If I update to
> the latest trunk, I get compiler errors about not defined devEth0. Then I
> see that there are quite several files having only small differences in
> their names that define this devEth0... I'm a bit confused now.
> If I do a fresh new checkout, the dependencies are correct and I can
> compile the httd demo.

The test script nut/tools/packaging/distcheck.lua reported a compile
problem for boards without Ethernet interface. As this sounded
reasonable to me, I didn't investigate this any further. Mmmh...


> Second my two script files, previously located in nut/tools/scripts are
> missing, so the arm-oocd burning option is no longer functioning.
> Who threw them away and why?

Not intentionally. Do you know the SVN revision number of your first
check-in of these files?

Harald

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[uprinz]

Hi!

The files never got checked in...

The problem is the following:
I work with several different repositories, some for private, the one
from ethernut at sourceforge and some for business.

When I wrote something for public in my other repositories, I merge it
with winmerge to the ethernut repository. Some times I copy over
directories... Unfortunately Winmerge copies over the .svn subdirectory
too. So the svn tree shows the correct version and symbols, but it
doesn't see, that this .svn is not from the upper directories svn.
And an svn commit simply skips this directory silently.

To bad!

So I add this scripts from nut/tools/flash now into the trunk and they
should be added to the beta as they work really smooth. Especially with
openocd 0.2.0.

Best regards
Ulrich

Harald Kipp schrieb:

> Ulrich Prinz wrote:
>
>> Two problems:
>> Can it be, that the emac drivers are bound in different files, or the
>> dependencies to nutconf have changed to bind them correctly? If I update to
>> the latest trunk, I get compiler errors about not defined devEth0. Then I
>> see that there are quite several files having only small differences in
>> their names that define this devEth0... I'm a bit confused now.
>> If I do a fresh new checkout, the dependencies are correct and I can
>> compile the httd demo.
>
> The test script nut/tools/packaging/distcheck.lua reported a compile
> problem for boards without Ethernet interface. As this sounded
> reasonable to me, I didn't investigate this any further. Mmmh...
>
>
>> Second my two script files, previously located in nut/tools/scripts are
>> missing, so the arm-oocd burning option is no longer functioning.
>> Who threw them away and why?
>
> Not intentionally. Do you know the SVN revision number of your first
> check-in of these files?
>
> Harald
>
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Ole Reinhardt-2]

Hi Ulrich,

> The files never got checked in...

Apropos svn: You recently checked in quite a lot of changes. Could you
please leave a short changelog Entry in the changelog too? Yes I know I
could generate a changelog from the svn entries, but I prefer at least a
short overview what was modified / added.

Thank you!

Ole

--
 _____________________________________________________________
|                                                             |
| Embedded-IT                                                 |
|                                                             |
| Ole Reinhardt        Tel. / Fax:        [phone] |
| Luisenstraße 29      Mobil:             [phone] |
| 57076 Siegen         eMail:    ole.reinhardt@... |
| Germany              Web:         http://www.embedded-it.de |
|_____________________________________________________________|

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Ethernut]

Ole Reinhardt wrote:
> Hi Ulrich,
>
...
>
> Apropos svn: You recently checked in quite a lot of changes. Could you
> please leave a short changelog Entry in the changelog too? Yes I know I
> could generate a changelog from the svn entries, but I prefer at least a
> short overview what was modified / added.

I feel guilty too.

Actually I like your conservative attitude regarding Changelog as well
as keeping plain Makefiles, which you demanded in a previous post.

Harald

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[uprinz]

Hi!

Sure, no problem. Most of the changes where automatically killed
trailing blanks.

Some files really where changed and yes, I'll add some comments next time.

Cheers, Ulrich

Ole Reinhardt schrieb:

> Hi Ulrich,
>
>> The files never got checked in...
>
> Apropos svn: You recently checked in quite a lot of changes. Could you
> please leave a short changelog Entry in the changelog too? Yes I know I
> could generate a changelog from the svn entries, but I prefer at least a
> short overview what was modified / added.
>
> Thank you!
>
> Ole
>

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Ethernut]

Hi Ulrich,

Ulrich Prinz wrote:

> Some files really where changed and yes, I'll add some comments next time.

Wrong ChangeLog. Obviously some explanations are required, may be
discussions also.

Until March 2009 we used ChangeLog to provide an easy to read overview
of all the changes. Furthermore we used the CVS keyword $Log$ to
automatically add the commit comments to the modified files.

This was most convenient for the reviewer, because each file contains a
history on top and the ChangeLog provides a complete overview. The other
side of the coin was, that the developer has to write comments for the
commit and additionally has to write a nice text in ChangeLog as well,
listing all the files that had been involved in a certain change.

Example:

2009-02-16  Harald Kipp  <spamrobot@...>

* include/arch/arm/at91_pmc.h, include/arch/arm/at91sam9xe.h:
Check for PLL B availability instead of target names.

One reason for changing from CVS to SVN was, that listing of files in
ChangeLog won't be required, because SVN revisions are atomic. I have to
admit, that I didn't understand that argument. And, because I didn't
understand, I did it wrong too in the past.

In order to make good use of atomic revisions, it is mandatory to fix
one problem after the other and commit each fix after the other. To give
a hypothetical example: Handshakes are not working on AT91 UARTs. As you
are working on these files already, you may also want to include DBGU
support in the AT91 UART driver. This should be done one after the
other. First, fix the handshake problem and commit all modified files.
Then add DBGU support and commit that one. This way the SVN history will
clearly list the fixes, enhancements etc. together with all files involved.

This way the SVN history will provide an acceptable replacement for the
ChangeLog file. It has the same contents.

Nevertheless, the Ethernut community got used to reading ChangeLog and
asked to continue it. While there is no need to list all modified files,
people would still like to have an easy to read comment like "I added a
new LED driver, which I tested on Atmel's SAM7X_EK".

Therefore I renamed ChangeLog to ChangeLog20090309 to freeze the CVS
version. Next I created a new ChangeLog, using a new format and adding
the request "What do you think about it?". Developers accepted it
without comment. The idea of the new format was to collect all
modifications under the 3 topics Fixed, Changed and Added for the user
who will upgrade to a new release. Frankly, I'm not satisfied with the
new format. It is difficult to read and less useful than the old
ChangeLog when searching for specific changes. And I'm not sure any
longer whether maintaining ChangeLog makes sense at all.

I don't see any reason, why the same comments in ChangeLog can't be used
in the commit as well. Specifically if we follow the strict rule to do
one modification after the other, as explained above. Initially I
expected to use this ChangeLog to provide a good summary for the casual
user. But look at it yourself. Does it really fit?

Long post, but it's nearly done. ;-) SVN no longer supports the keyword
$Log$, so there will be no history inside the files anymore. The history
may become misleading, if no longer updated. From time to time I already
replaced $Log$ by $Id$ in several source files, removing this old
history. Nothing is lost, because SVN took over the CVS history.
Recently I noticed, that some developers manually added these entries. I
do not think that this is a good idea, because it won't provide a good
history unless every developers maintains it.

More about $Log$:
http://subversion.tigris.org/faq.html#log-in-source

Thanks,

Harald

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion