Hi,
I am trying to write a PCI ethernet driver for FreeBSD 3.4 release.
I have some questions
1. How can I convert physical address to virtual address . What I want
is to read the physical address from the device register and to copy it
to host memory. From my earlier post I found that I
Hey all,
I have been trying to port some code to FreeBSD which currently runs under
Linux (and to some degree, Solaris). Since I'm a longtime FreeBSD user,
I'm pretty excited to get a chance to port to FreeBSD.
The program I'm working on uses both POSIX threads and ISO C++ (including
hi, there!
On Fri, 25 Aug 2000, Bryan K. Ogawa wrote:
1. I had seen an email in the mailing list archives which asserted that
C++ exceptions have been broken since August 1999 in the multithread case
-- does anyone know what the status in 4.1-STABLE and -CURRENT are? I've
managed to get
Sorry, I posted this already in 'questions' but since it is very urgent to
my tape read back withing the next couple of hours I'm posting my plea
here also:
I'm trying to read a DAT tape with important backup data.
The device is a DEC TLZ04.
sa0 at ncr0 bus 0 target 4 lun 0
sa0: DEC TLZ04
* Pran Joseph [EMAIL PROTECTED] [000825 00:11] wrote:
Hi,
I am trying to write a PCI ethernet driver for FreeBSD 3.4 release.
I have some questions
1. How can I convert physical address to virtual address . What I want
is to read the physical address from the device register and to
If i do a perlcc test.pl i get the folllowing , in CURRENT ?
Must i define something beforehand, or is it broken ?
-Wl,-E -lperl -lm -L/usr/libdata/perl/5.6.0/mach/CORE -lperl -lm -lc -lcrypt
/usr/libdata/perl/5.6.0/mach/auto/IO/IO.so
/usr/libdata/perl/5.6.0/mach/auto/Fcntl/Fcntl.so
Hello,
I have some ideas to improve fork()-ing and getting rid of zombie processes.
This things mentioned here are proposed of a man that do not know very well
(author means 'the depths' of) BSD kernel source although he have some ex-
pirience with it (mainly in reading it :-).
By definition
[EMAIL PROTECTED] wrote:
Hello,
I have some ideas to improve fork()-ing and getting rid of zombie processes.
This things mentioned here are proposed of a man that do not know very well
(author means 'the depths' of) BSD kernel source although he have some ex-
pirience with it (mainly in
* [EMAIL PROTECTED] [EMAIL PROTECTED] [000825 03:14] wrote:
Hello,
I have some ideas to improve fork()-ing and getting rid of zombie processes.
This things mentioned here are proposed of a man that do not know very well
(author means 'the depths' of) BSD kernel source although he have some
Hi,
I have committed orthognal part of ACPI driver.
The rest part will be committed after a few days.
I put the part at URL:http://people.freebsd.org/~takawata/sysdiff.
This can be applied for HEAD. Please test and report about it if there
is serious problem,such as breaking build.
Thanks.
I have some ideas to improve fork()-ing and getting rid of
zombie processes.
This things mentioned here are proposed of a man that do
not know very well
(author means 'the depths' of) BSD kernel source although
he have some ex-
pirience with it (mainly in reading it :-).
By
* Yevmenkin, Maksim N, CSCIO [EMAIL PROTECTED] [000825 05:59] wrote:
[snip]
If a parent that has zombie children exits the kernel will attach them
to init (I haven't checked, but this is the common unix solution).
init will be calling waitpid to clear zombies automagically.
this issue is unrelated to threads. FreeBSD stock g++ 2.95.2 compiler
uses -fsjlj-exceptions mechanism for exception handling which is broken
(g++ sometimes generates incorrect code even without any optimization
options given). It is not FreeBSD-specific behaviour. gcc GNATS has
bug report
On Fri, Aug 25, 2000 at 10:52:49AM +0200, Christoph Kukulies wrote:
Sorry, I posted this already in 'questions' but since it is very urgent to
my tape read back withing the next couple of hours I'm posting my plea
here also:
Ooops. I must have been very nervous about getting my tape read
On Fri, Aug 25, 2000 at 02:19:28PM +, [EMAIL PROTECTED] wrote:
Hello,
Hi ix
By definition zombie is a process entry in proc table that wasn't released
by wait*() called form the parent's code. So all we need to do is to ensure
A zombie can only occur with a *live* parent. If the
* Robert Watson [EMAIL PROTECTED] [000821 18:01] wrote:
For reference, my recollection is that peemption-aware userland thread
libraries tend to make alot of timer syscalls, losing some of the
advantage of being a userland thread library (low context switch cost, few
transistions
From: "Bryan K. Ogawa" [EMAIL PROTECTED]
If anyone who knows about the state of the FreeBSD threads implementation
could go through it and check it for factual errors, missing bits, etc.
then that would be great.
in your section about common reentrant extensions, you mention the IPv6
apis.
Hello!
I am a SysAdmin at GTE, 'er Verizon, and we are doing something
simular. We tried using the freebie stuff with Xfree86 4.0.1 but found
it to be extreamly buggy... both on Linux and FreeBSD. The solution we
found works best is paying the 129 bucks and getting the drivers from
hi, there!
On Fri, 25 Aug 2000, Alexander N. Kabaev wrote:
There was a bug in -fsjlj-exceptions code generation related to shared
libraries and to best of my knowledge the correct fix has been imported into
the official gcc CVS tree and was merged into FreeBSD some time ago. Are there
any
In message [EMAIL PROTECTED] Pran Joseph writes:
: 1. How can I convert physical address to virtual address . What I want
: is to read the physical address from the device register and to copy it
: to host memory. From my earlier post I found that I can use vtopys
: macro to convert virtual to
'Alfred Perlstein' wrote:
int
sigchld_handler(int)
{
while (waitpid(-1, NULL, 0) || errno == EINTR)
;
}
Even more paranoid would be
int
sigchld_handler(int)
{
int e = errno;
while (waitpid(-1, NULL, 0) || errno == EINTR)
;
* Ben Smithurst [EMAIL PROTECTED] [000825 10:15] wrote:
'Alfred Perlstein' wrote:
int
sigchld_handler(int)
{
while (waitpid(-1, NULL, 0) || errno == EINTR)
;
}
Even more paranoid would be
int
sigchld_handler(int)
{
int e = errno;
while
'Alfred Perlstein' wrote:
int
sigchld_handler(int)
{
while (waitpid(-1, NULL, 0) || errno == EINTR)
;
}
actually, shouldn't you use WNOHANG when calling waitpid() there? What
I normally do is
int e = errno;
while (waitpid(-1, NULL, WNOHANG) 0)
On Fri, Aug 25, 2000 at 10:52:49AM +0200, Christoph Kukulies wrote:
Sorry, I posted this already in 'questions' but since it is very urgent to
my tape read back withing the next couple of hours I'm posting my plea
here also:
I'm trying to read a DAT tape with important backup data.
The
On Fri, Aug 25, 2000 at 11:52:18AM -0400, Tim Grzechowski wrote:
We tried using the freebie stuff with Xfree86 4.0.1 but found
it to be extreamly buggy... both on Linux and FreeBSD.
Could you describe `extremely buggy'? Did you open any problem reports
with the XFree86 guys?
I have been
I have committed orthognal part of ACPI driver.
The rest part will be committed after a few days.
I put the part at URL:http://people.freebsd.org/~takawata/sysdiff.
This can be applied for HEAD. Please test and report about it if there
is serious problem,such as breaking build.
It seems
If i do a perlcc test.pl i get the folllowing , in CURRENT ?
Must i define something beforehand, or is it broken ?
I'll take a look...
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the
Reposted to -HACKERS
Hiya...
I am having an issue with the wd driver (from FBSD 3.51). Once a customer
kernel (having the flags 0xa0ffa0ff for wd) is booted, I get screen-full's
of this error message when there is any hard drive access:
DMA failure, DMA status 5active
I can "slow down" or
Hello,
[please Cc: to me, since I'm not subscribed to this list. Thanks]
are there plans to replace FreeBSD's libc with GNU glibc in the near
or medium future? Linux moved also from it's own libc5 to glibc (=libc6)
some time ago and it may be useful to do the same in FreeBSD too.
The reason
On Sat, 26 Aug 2000, Farid Hajji wrote:
Hello,
[please Cc: to me, since I'm not subscribed to this list. Thanks]
are there plans to replace FreeBSD's libc with GNU glibc in the near
or medium future?
I think I can safely say:
"No."
Kris
--
In God we Trust -- all others must submit an
[please Cc: to me, since I'm not subscribed to this list. Thanks]
are there plans to replace FreeBSD's libc with GNU glibc in the near
or medium future? Linux moved also from it's own libc5 to glibc (=libc6)
some time ago and it may be useful to do the same in FreeBSD too.
No, that is not
* Farid Hajji [EMAIL PROTECTED] [000825 21:03] wrote:
Hello,
[please Cc: to me, since I'm not subscribed to this list. Thanks]
are there plans to replace FreeBSD's libc with GNU glibc in the near
or medium future? Linux moved also from it's own libc5 to glibc (=libc6)
some time ago and
Kris Kennaway wrote:
On Sat, 26 Aug 2000, Farid Hajji wrote:
Hello,
[please Cc: to me, since I'm not subscribed to this list. Thanks]
are there plans to replace FreeBSD's libc with GNU glibc in the near
or medium future?
I think I can safely say:
"No."
Not only "No" but
On Saturday, August 26, 2000, Farid Hajji wrote:
are there plans to replace FreeBSD's libc with GNU glibc in the near
or medium future? Linux moved also from it's own libc5 to glibc (=libc6)
some time ago and it may be useful to do the same in FreeBSD too.
There are no such plans for that
On Fri, 25 Aug 2000, Jamie Hermans wrote:
I am having an issue with the wd driver (from FBSD 3.51). Once a customer
kernel (having the flags 0xa0ffa0ff for wd) is booted, I get screen-full's
of this error message when there is any hard drive access:
DMA failure, DMA status 5active
I
Thanks for your help !
If someone would be kind enough to answer them, I have a few other questions.
I'm currently trying to modify sysctl_kern_proc() function in
src/sys/kern/kern_proc.c
But, to modify it, I must understand it first ;-)
First, this sysctl is supposed to give the list of the
37 matches
Mail list logo
