No comment or objection? Then, I'll commit the patch tomorrow.
ozaki-r
On Wed, Jul 9, 2014 at 12:55 PM, Ryota Ozaki ozak...@iij.ad.jp wrote:
On Tue, Jul 8, 2014 at 12:54 PM, Ryota Ozaki ozak...@iij.ad.jp wrote:
Hi,
A new patch has come: http://www.netbsd.org/~ozaki-r/mpsafe-bridge.diff
I
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.NetBSD.org, a NetBSD/amd64 host,
using sources from CVS date 2014.07.13.14.56.56.
An extract from the build.sh output follows:
Source directory:
Today I've attempted to try out the new i915drmkms support on NetBSD
6.99.47-CURRENT. I've built the DRMKMS kernel conf and installed its
modules, and attempted to boot.
Unfortunately, despite having all relevant debug options checked, it
seems that NetBSD kernel simply freezes after displaying
On behalf of the release engineering team, I am happy to announce that
the release process for NetBSD 7.0 is now underway.
We will be creating the netbsd-7 CVS branch on or about July 26th, just
under two weeks from today. The creation of this branch will mark the
start of the Beta period,
On 7/13/14, 11:28 AM, David Mackay wrote:
Today I've attempted to try out the new i915drmkms support on NetBSD
6.99.47-CURRENT. I've built the DRMKMS kernel conf and installed its
modules, and attempted to boot.
Unfortunately, despite having all relevant debug options checked, it
seems that
For the time being, I have decided to create a custom shell script in the
spirit of etcmanage, after looking over BUILD-NetBSD; perhaps an INSTALL-NETBSD
custom shell script will follow. I do a large amount of cross-building (my
NetBSD compiling box is an Ubuntu machine), and I'm not sure how
Hello all,
Although my question is specific to the Raspberry Pi, I can imagine anyone who
has specific network cards- or hardware requiring firmware during installation-
asking this question.
I have a Raspberry Pi Model A, which does not contain onboard Ethernet. In
order to get a network
On Sun, Jul 13, 2014 at 09:43:50PM +, thor0...@comcast.net wrote:
Editing $SRC_ROOT/distrib/evbarm/instkernel/sshramdisk/mtree.conf
seems to be the way to add the relevant directory into the ramdisk.
However, is there a way to tell ./build.sh or the Makefiles to add the
relevant firmware
The list file in the same directory is what you are looking for.
Beautiful, thanks! I notice that the standard RAMdisks are missing the
mtree.conf file. Is altering the list file alone enough to add directories to
the standard RAMdisk (not sshramdisk*), or do I have to create my own
mtree.conf
I've updated my sources to include this change. Unfortunately, it has
not made a difference.
Thanks for letting me know about it, though.
On Sun, Jul 13, 2014 at 8:18 PM, Jeff Rizzo r...@tastylime.net wrote:
On 7/13/14, 11:28 AM, David Mackay wrote:
Today I've attempted to try out the new
Updating src tree:
P src/distrib/sets/lists/base/mi
P src/distrib/sets/lists/debug/ad.arm
P src/distrib/sets/lists/debug/ad.mips
P src/distrib/sets/lists/debug/ad.powerpc
P src/distrib/sets/lists/debug/md.sparc64
P src/distrib/sets/lists/man/mi
P src/etc/rc.d/named
P
On Sun, Jul 13, 2014 at 10:20:46PM +, thor0...@comcast.net wrote:
*I altered both mtree.conf to add the libdata subtree, and lists
to tell ./build.sh/make to copy the firmware: COPY
${NETBSDSRCDIR}/external/realtek/urtwn/dist/rtl8192cfw.bin
libdata/firmware/if_urtwn/rtl8192cfw.bin
That
12 matches
Mail list logo
