FreeBSD vs Linux framebuffer

Hi Kazutaka, hackers, As adviced by the GGI community, I will first try to port libGGI to the FreeBSD framebuffer. Before I look deeper into the sources, what are the main differencies between Linux and FreeBSD designs? Are the interfaces similar? Regards, Nicholas -- Nicolas Souchu Alcôve

Any actual shipping ATM cards supported by FreeBSD 4.x and higher?

Fore systems web site dumps you into Marconi's site, and a search there doesn't find the word ATM. Efficient Networks page doesnt list the card on the products page any more. So barring those 2, which are the only 2 listed in the release notes, where can I get ATM cards that will work?

dlopen()

Greetings. Is it safe to remove the *.so file after it is loaded into the process space and addresses to its functions are gotten? I've tested this and have no problems so far. I need this to implement the "hot swap" of the dynamic loading libraries. Thanks, Dmitry To Unsubscribe: send

Re: dlopen()

Dmitry Sychov wrote: Greetings. Is it safe to remove the *.so file after it is loaded into the process space and addresses to its functions are gotten? It's safe to remove it as soon as it's been opened. The file will still exist in the filesystem, only there won't be any references to it

Re: dlopen()

On Thu, Nov 23, 2000 at 01:40:34PM +, Konstantin Chuguev wrote: Dmitry Sychov wrote: Greetings. Is it safe to remove the *.so file after it is loaded into the process space and addresses to its functions are gotten? It's safe to remove it as soon as it's been opened. The file

Re: dlopen()

hi, there! On Wed, 22 Nov 2000, Dmitry Sychov wrote: Is it safe to remove the *.so file after it is loaded into the process space and addresses to its functions are gotten? yes /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the

Re: dlopen()

Peter Pentchev wrote: Is it safe to remove the *.so file after it is loaded into the process space and addresses to its functions are gotten? It's safe to remove it as soon as it's been opened. The file will still exist in the filesystem, only there won't be any references to it

page coloring

Hi. Isn't the page coloring algoritm in _vm_page_list_find totally bogus? It skips queue pq[index PQ_L2_MASK]. If it doesn't find page with desired color, it allocates page with nearest color - as a result there are two pages with same color mapped at two adjacent virtual adresses - this is

subscribe

subscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Re: Any actual shipping ATM cards supported by FreeBSD 4.x andhigher?

On Thu, 23 Nov 2000, Jaye Mathisen wrote: Fore systems web site dumps you into Marconi's site, and a search there doesn't find the word ATM. Yeah, it was a pretty sad day when the Fore site changed from ATM products to ... actually, I don't know *what* they are selling now. I hope otherwise,

Re: 2 pci , 1 isa, same type NIC makes freebsd seems to be confused

Motomichi Matsuzaki wrote: These separated devclass leads to confusable situation. Drivers which have same name (such like 'ed') should share one devclass, or multiple 'ed0' appear on the host. Sadly, this type of mistakes are widely spreaded on the tree. That's probably because it's

Re: BSD's random.c dicey on the Alpha

Anyone want to have a look at this? It's from the GNU awk maintainer. Without knowing which random.c it was, it's hard to judge :-) Also not knowing what the intended use is, it's hard to recommend something. I'd guess src/lib/libc/stdlib/random.c I'll bury it in my TODO. M -- Mark

Re: porting a Linux app

"Daniel C. Sobral" wrote: Andrew Otwell wrote: gcc -static -I /pathto/new/include -L /pathto/new/lib sourcefile.c -nostdlib -nostdinc and don't forget to compile the libries on freeBSD..you can't just use the Linux ones -- Daniel C. Sobral(8-DCS) [EMAIL

Ethernet de driver problem on 3.5 stable

I have run into an issue with the de driver and Dlink quad cards under 3.5 stable. Despite the messages from the driver, claiming to be in full duplex, (see trimmed dmesg output below) it's not. I removed a working Intel fxp card from a system and installed the Dlink quad card. Same cable,

Re: page coloring

On Thu, Nov 23, 2000 at 12:48:09PM -0800, Mike Smith wrote: Isn't the page coloring algoritm in _vm_page_list_find totally bogus? No, it's not. The comment is, however, misplaced. It describes the behavior of an inline function in vm_page.h, and not the function it precedes.

Re: Ethernet de driver problem on 3.5 stable

I have run into an issue with the de driver and Dlink quad cards under 3.5 stable. Despite the messages from the driver, claiming to be in full duplex, [...] Is there a known problem with the Dlinks or is this a possible issue in the driver? [...] Probing for devices on PCI bus 2: de0:

Re: SVR4 missing syscall

"Walter C. Pelissero" wrote: I'm trying to run a SCO SVR4 executable on FreeBSD but I get a SIGSYS (invalid system call) at the very beginning. Here is the kdump: 39525 ktrace RET ktrace 0 39525 ktrace CALL sigprocmask(0x1,0x28061000,0x28061010) 39525 ktrace RET

Re: dlopen()

In article [EMAIL PROTECTED], Konstantin Chuguev [EMAIL PROTECTED] wrote: Peter Pentchev wrote: So the original poster's question is better translated as 'does the dynamic loader ever close and reopen a file after the initial loading, so it could accidentally open the new version of the

crash on 4.2-stable (sendto() system call)

Hi, got a crash on 4.2-stable. the machine was running 4.1.1-stable and had no problem at all. 10 hours after upgrade to 4.2-stable I got a vmcore. Here it's the trace and could someone take a look, it looks like it was the sendto() call triggered the crash but I don't know how to reproduce

Re: crash on 4.2-stable (sendto() system call)

Hello, Can you please also get the instruction at which the page fault occured? You can try "where" from gdb or you can get the instruction pointer from the original page fault message and then you can probably "disassemble fr_makefrip" and get us the contents around the

Re: crash on 4.2-stable (sendto() system call)

* Bosko Milekic [EMAIL PROTECTED] [001123 14:51] wrote: Hello, Can you please also get the instruction at which the page fault occured? You can try "where" from gdb or you can get the instruction pointer from the original page fault message and then you can probably

Re: crash on 4.2-stable (sendto() system call)

On Thu, 23 Nov 2000, Alfred Perlstein wrote: -* Bosko Milekic [EMAIL PROTECTED] [001123 14:51] wrote: - - Hello, - - Can you please also get the instruction at which the page fault - occured? You can try "where" from gdb or you can get the instruction - pointer from the original

Re: fclose vs ferror (from libc/getcap)

Matt Dillon wrote: [...] In today's world the standard is: When you free() something, that's it.. it's gone. When you fclose() something or otherwise terminate a structure, it's gone. Anything else is illegal. *internally* our libc assumes that ferror() is legal

DMA to user process address space!!!

AFAMUG, all user processes are allocated from the virtual memory. so DMA to that doesn't make sense. but is there some way, i can let the kernel know i am DMAing to an address location and hence keep it in main memory until some x seconds??