Most of the userland and the kernel in NetBSD 7.0 seem to be built with -mfloat-abi=soft (this is from earmv6hf). Indeed, if you look at the Makefile generated when you're preparing to build a new kernel you will see -mfloat-abi=soft is defined. For example the openssl in base has the following performance characteristics:

Doing md4 for 3s on 16 size blocks: 91199 md4's in 2.68s

If I build a new openssl with -march=armv6k -mfloat-abi=hard -mfpu=vfp' in my/usr/pkg/etc/mk.conf`, I get the following:

Doing md4 for 3s on 16 size blocks: 221820 md4's in 2.85s

That's quite a substantial improvement. Could you please tell me the reasoning behind not doing this in the default distribution?


Comment by josh64 late Wednesday night, October 15th, 2015

Thanks for all the great work and for updating your instructions to reflect the new RPI2 images. Which by the way are awesome and right on par now with what the top competition has, in other words *dora has nothing us now with regards to tuning with gcc on this arch.

Last week I took the armv7 gzimg and added the new RPI2 kernel from another snapshot. Wow it worked, and I felt pretty special until the next time I looked 5 minutes later...and I saw I had just took the long route to reproduce what was already done in the new armv7 rpi2 images. LOL.

On a site note. Please consider updating the "Installation" section example to clarify HEAD/Current images vs Stable. If it's important.

Currently it reads:

"The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example,"

I would change the "netbsd-7" to "HEAD" as below, if I'm understanding correctly.

"The HEAD/current directory build will be under HEAD/YYYYMMDDHHMMZ/ (for example,"

NetBSD 4 Ever!

Comment by George early Saturday morning, August 15th, 2015

Determine first what interfaces are available:

ifconfig -l

Add to /etc/rc.conf:

# Do not wait for lease; useful if no network is within reach, so boot will not hang
# select the appropriate interface (-i) for your wifi card. (i.e. -i wpi0)
wpa_supplicant_flags="-B -i wpi0 -c /etc/wpa_supplicant.conf"
Comment by Frank Thursday afternoon, April 16th, 2015

Can anyone explain if all files (including the subdirectory overlays/ ) need to be copied? "Copy all files except 'kernel*.img' into /boot and reboot"

Or would a subset be sufficient?

Thanks very much -- Tobi

Comment by Tobias N. Sasse at lunch time on Wednesday, April 15th, 2015
Is this still an open project? Or has someone started working on this already? Where does one contact for reviews/submits el al?
Comment by Manali Monday evening, April 13th, 2015
Perhaps it's worth considering the Lumina desktop environment from PC-BSD.
Comment by J. Lewis Wednesday afternoon, April 8th, 2015
Can someone please post link to netbsd 7.0 sources? I want to compile latest netbsd for my raspberry pi 2 board.
Comment by alakesh late Sunday afternoon, April 5th, 2015

Thoughts from a passers-by:

Let the output formats (we need most!) dictate the requirements of the tool.
Let us end up with building a printing press. Let us forget a writer writes with a Fountain pen to concentrate on content. To getaway with distractions.
Instead let us provide him a letter case. To let him think about each single letter independently. Instead of thinking of the content.
If he has kept up till now, let us further distract him: Let him set the printing press to output almost any book format available.
Of course, none supports that letter combination he minutely composed earlier. Let him think about which format to choose or which letters to loose!

A writer needs a tool which concentrates his thought. A printing press expands thought.
What will the writer do if one gives the writer a printing press?

Why should the available book formats define the pen of the writer? 'Content rules format.'

I see a collection of printing presses. They can do a lot.
I read: They don't do the job 'software documentation'.
But what does this all have to do with solving the task 'software documentation'?
Nothing. One needs to specify what 'software documentation' is before choosing the tool.
To me it is:

  1. Hierarchy
    1. Headings
    2. Lists
  2. Descriptive text
  3. Non-descriptive text (quotes)
    1. Inline
    2. Multiline
  4. References
    1. Internal
    2. External
      1. Author, Title, Date, Location
      2. URI
  5. Images

Blocks of texts are organised in an hierarchy (a1).
Block of texts consist of descriptive (b) and non-descriptive elements (quotes) (c).
A descriptive element (b) explains stuff. A non-descriptive (c) is either input or output of the software. It may be inline (c1) or multiline (c2).
A descriptive element may contain lists (a2). It may contain references to (d1) the hierarchy itself or (d2) to external sources.
I leave it to some higher power whether images (e) are required.
The plain text should be (1) indented and (2) broken incorporating the hierarchy (a1) (Why is this not the editor's job? Consistency.).

That's it.

'But I need to highlight some description text.' No, you don't.
If it's important it should be reflected by the hierarchy anyway. Still, not satisfied? Then, look at your keyboard:
o r s p a c e.
O R B O T H.

You haven't seen anything. Continue your walk.

Comment by Benjamin late Tuesday evening, March 31st, 2015

if you get the following error while trying to fetch sets;

ftp: Can't LOOKUP `': Temporary failure in name resolution

Please use the nyftp's IP address instead:

As reported by

Comment by Youri Sunday afternoon, March 22nd, 2015
Really looking forward to the future of this port! I'd love to build a fileserver with my C1 using NetBSD as the OS.
Comment by Bo terribly early Monday morning, March 9th, 2015
Add a comment