Re: Tar output mode for installworld

On 7/15/07, Tim Kientzle <[EMAIL PROTECTED]> wrote: Ulrich Spoerlein wrote: > Simple and elegant. It would also do away with those base.aa, base.ab, > etc. madness. I'm confused. base.aa, etc, are a tar file, so I don't entirely understand how this would be different? The current installer doe

Problem with Broadcom 5704 B1 on amd64 6.2 release

Greetings, I've run into a problem with the onboard Broadcom 5704 NetXtreme nics on a Tyan S2891 Thunder K8SRE motherboard. Here is the relevant dmesg output to show the error: pcib5: at device 11.0 on pci8 pci10: on pcib5 pcib5: memory: end (de1f) < start (48739b2de10) pcib5: memory:

Re: Debugging times

David Malone <[EMAIL PROTECTED]> writes: >> Yes, I'll test them. >> >> The problem is - the same kernel works when booted off a hard drive, so >> unless the VMWare BIOS is very messed up (it's the first time I see such >> problems) it may not help. Please, scatter debug printf's around so I >> ca

Re: add closefrom() call

* Julian Elischer <[EMAIL PROTECTED]> wrote: > Ed Schouten wrote: >> Woops! Sorry for responding this late, but it looks like I didn't >> explain myself good enough. Sorry. :) To rephrase myself: >> Wouldn't it be better to just implement fcntl(..., F_CLOSEM, ...) in the >> kernel and make closefro

Re: Setting up development environment

In message: <[EMAIL PROTECTED]> "Brian Chu" <[EMAIL PROTECTED]> writes: : I have a question about indentation. In the previously supplied : .emacs hook, tabs are represented by 8 spaces. Most of the kernel : code, however, actually uses the tab character. : : Are both forms acceptabl

Re: Tar output mode for installworld

In message: <[EMAIL PROTECTED]> Paul Schenkeveld <[EMAIL PROTECTED]> writes: : On Sat, Jul 14, 2007 at 11:28:05PM -0700, Tim Kientzle wrote: : > >>>This is easy to implement ... just build : > >>>a description of the final archive in a nice verbose : > >>>text format such as: : > >> : >

Re: Tar output mode for installworld

On 07/15/07 16:20, Tim Kientzle wrote: Ulrich Spoerlein wrote: On Sat, 14.07.2007 at 23:28:05 -0700, Tim Kientzle wrote: #%ntree bin/echo uid=0 gid=0 group=wheel contents=my/bin/echo ... create a tarball with tar -czf system.tgz @specification.ntree or install directly from the specificatio

Re: Setting up development environment

Hm. It doesn't always replace 8 spaces with tabs (for files that are heavily spaced-indented), but I suppose that using `M-x tabify` would do the trick. Thanks! Brian On 7/15/07, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: "Brian Chu" <[EMAIL PROTECTED]> writes: > I have a question about i

Re: loading a firmware image

Maslan wrote: The firmware is bundled in a seperate kernel module that can be loaded, read and then unloaded. See src/sys/modules/iwifw/iwi_bss for an example of the Makefile magic that creates the kld. if i wrote FIRMWS = filename:shortname:version in the Makefile then i should user firmware_g

Re: add closefrom() call

Ed Schouten wrote: * Julian Elischer <[EMAIL PROTECTED]> wrote: Ed Schouten wrote: Wouldn't it be better to just implement it through fcntl() and implement closefrom() in libc? that's a possibility but I personally thing the huge difference in efficiency makes it worth putting it in the kerne

Re: loading a firmware image

The firmware is bundled in a seperate kernel module that can be loaded, read and then unloaded. See src/sys/modules/iwifw/iwi_bss for an example of the Makefile magic that creates the kld. if i wrote FIRMWS = filename:shortname:version in the Makefile then i should user firmware_get("shortname")

Re: loading a firmware image

Have you seen the file2c(1) utility? I don't want to run into license troubles. -- System Programmer -- I'm Searching For Perfection, So Even If U Need Portability U've To Use Assembly ;-) -- http://libosdk.berlios.de/wiki/ ___ freebsd-hackers@freebsd.

Re: loading a firmware image

On Sun, Jul 15, 2007 at 11:35:12PM +0300, Maslan wrote: > Hello, > > What is the best way to load a firmware image (microcode) ? > AFAIK I've to load the image file first in memory then call > firmware_register() but my problem is how should i load the image in > memory ?? The firmware is bundled

Re: loading a firmware image

Maslan wrote: >my problem is how should i load the image in > memory ?? Have you seen the file2c(1) utility? signature.asc Description: OpenPGP digital signature

Re: Tar output mode for installworld

Ulrich Spoerlein wrote: On Sat, 14.07.2007 at 23:28:05 -0700, Tim Kientzle wrote: #%ntree bin/echo uid=0 gid=0 group=wheel contents=my/bin/echo ... create a tarball with tar -czf system.tgz @specification.ntree or install directly from the specification file using tar -xvpf specification.n

Re: add closefrom() call

* Julian Elischer <[EMAIL PROTECTED]> wrote: > Ed Schouten wrote: >> Wouldn't it be better to just implement it through fcntl() and implement >> closefrom() in libc? > > that's a possibility but I personally thing the huge difference in > efficiency > makes it worth putting it in the kernel. > Qui

Re: Setting up development environment

"Brian Chu" <[EMAIL PROTECTED]> writes: > I have a question about indentation. In the previously supplied > .emacs hook, tabs are represented by 8 spaces. No, Emacs automatically converts spaces to tabs according to the current setting of tab-width, which is normally 8. DES -- Dag-Erling Smørgr

loading a firmware image

Hello, What is the best way to load a firmware image (microcode) ? AFAIK I've to load the image file first in memory then call firmware_register() but my problem is how should i load the image in memory ?? Thanks alot -- System Programmer -- I'm Searching For Perfection, So Even If U Need Porta

Re: Debugging times

On Sun, Jul 15, 2007 at 11:37:57AM +0200, Dominique Goncalves wrote: > >Yes, it does! Setting ct.dow to -1 fixes the time in a correct way. > It works also for me with qemu 0.9.0. Great - I'll work on getting it merged in. David. ___ freebsd-ha

Re: Tar output mode for installworld

On 2007-07-14 19:45, Tim Kientzle <[EMAIL PROTECTED]> wrote: >On 2007-07-14 13:20, Tim Kientzle <[EMAIL PROTECTED]> wrote: >>> >>> >>> This is easy to implement using a ... text format such as: >>> bin/sh file /usr/obj/usr/src/bin/sh >>> bin/s

Re: Setting up development environment

I have a question about indentation. In the previously supplied .emacs hook, tabs are represented by 8 spaces. Most of the kernel code, however, actually uses the tab character. Are both forms acceptable? If not, anyone willing to share their tab-character-tabs .emacs c hook? Thanks, Brian O

Re: Tar output mode for installworld

On Sat, 14.07.2007 at 23:28:05 -0700, Tim Kientzle wrote: > #%ntree > bin/echo uid=0 gid=0 group=wheel contents=my/bin/echo > > I think this should form a reasonable basis against which > to implement tar output for installworld. I would actually > suggest building the specification file at

Re: Tar output mode for installworld

Paul Schenkeveld wrote: ... read, extract, etc, a format I'm calling "ntree" for now. ... lines have the following format: = = ... Where key is one of: time ... gid,uid ... gname,uname ... mode ... content ... ... I've been playing a lot with automating and customizing the build/distribu

Re: Tar output mode for installworld

On Sat, Jul 14, 2007 at 11:28:05PM -0700, Tim Kientzle wrote: > >>>This is easy to implement ... just build > >>>a description of the final archive in a nice verbose > >>>text format such as: > >> > >>...which is done by NetBSD for the unprivileged release building via > >>build.sh. Anyone interest

Re: Debugging times

Hi, On 7/13/07, Ivan Voras <[EMAIL PROTECTED]> wrote: David Malone wrote: > Ah - that's interesting. Could you look for the comment in > src/sys/i386/isa/clock.c that says: > > /* Should we set dow = -1 because some clocks don't set it correctly? */ > > and add a line afterwards to say: >