Sean Bryant [EMAIL PROTECTED] writes:
I'm writing some cd buring software using burncd as a reference. I was
wondering if its possible to detect opening and closing of the doors.
Unfortunately, no. The drive may not even have a door.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
Dag-Erling [iso-8859-1] Smo/rgrav wrote:
Sean Bryant [EMAIL PROTECTED] writes:
I'm writing some cd buring software using burncd as a reference. I was
wondering if its possible to detect opening and closing of the doors.
Unfortunately, no. The drive may not even have a door.
DES
--
Intron [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
Sean Bryant [EMAIL PROTECTED] writes:
I'm writing some cd buring software using burncd as a reference.
I was wondering if its possible to detect opening and closing of
the doors.
Unfortunately, no. The
Dag-Erling [iso-8859-1] Smo/rgrav wrote:
Intron [EMAIL PROTECTED] writes:
Dag-Erling Smo/rgrav [EMAIL PROTECTED] writes:
Sean Bryant [EMAIL PROTECTED] writes:
I'm writing some cd buring software using burncd as a reference.
I was wondering if its possible to detect opening and closing of
Intron [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
Intron [EMAIL PROTECTED] writes:
However, software can command the drive to open/close its door.
This is not what Sean wants.
I want to tell Sean that he is not worth spending time in finding
how to detect the
Dag-Erling [iso-8859-1] Smo/rgrav wrote:
Intron [EMAIL PROTECTED] writes:
Dag-Erling Smo/rgrav [EMAIL PROTECTED] writes:
Intron [EMAIL PROTECTED] writes:
However, software can command the drive to open/close its door.
This is not what Sean wants.
I want to tell Sean that he is not worth
Hi!
I'm trying to write kernel code where exceptions are unavoidable.
To clarify , I need to recover after GP (general protection) exception
on i386 cpu and return an error in that case.
Unfortunately, looking in trap.c kernel code I can't find any exception
handling mechanism except inserting
Intron [EMAIL PROTECTED] writes:
Dag-Erling Smo/rgrav [EMAIL PROTECTED] writes:
How does ridiculing me help Sean?
Can your unilateral judgement give real help to Sean?
Welcome to my kill file. Enjoy your stay.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
i've got a single board computer with VIA C3 Samuel 2, 256MB RAM and 4
onboard Realtek 8139C+ NICs. I'm attempting to get FreeBSD 6.1-STABLE
working on them, but the realtek NICs just don't seem to want to work.
booting up led to a kernel trap with the following,
rlphy0: RealTek internal
Dag-Erling [iso-8859-1] Smo/rgrav wrote:
Intron [EMAIL PROTECTED] writes:
Dag-Erling Smo/rgrav [EMAIL PROTECTED] writes:
How does ridiculing me help Sean?
Can your unilateral judgement give real help to Sean?
Welcome to my kill file. Enjoy your stay.
DES
--
Dag-Erling Smo/rgrav - [EMAIL
On Mon, Aug 14, 2006 at 05:22:23PM +0800, Dinesh Nair wrote:
i've got a single board computer with VIA C3 Samuel 2, 256MB RAM and 4
onboard Realtek 8139C+ NICs. I'm attempting to get FreeBSD 6.1-STABLE
working on them, but the realtek NICs just don't seem to want to work.
booting up
On 08/14/06 17:22 Dinesh Nair said the following:
i've got a single board computer with VIA C3 Samuel 2, 256MB RAM and 4
onboard Realtek 8139C+ NICs. I'm attempting to get FreeBSD 6.1-STABLE
working on them, but the realtek NICs just don't seem to want to work.
booting up led to a kernel
On 08/14/06 18:39 Pyun YongHyeon said the following:
Recent changes from wpaul disabled re_diag() routine by default so it
i disabled re_diag() in /usr/src/sys/dev/if_re.c, and that caused the
kernel trap to go away, as per my original email. also, see my followup
email (to myself) in which
On Mon, Aug 14, 2006 at 06:55:58PM +0800, Dinesh Nair wrote:
On 08/14/06 18:39 Pyun YongHyeon said the following:
Recent changes from wpaul disabled re_diag() routine by default so it
i disabled re_diag() in /usr/src/sys/dev/if_re.c, and that caused the
kernel trap to go away, as
On 08/14/06 19:09 Pyun YongHyeon said the following:
really sucks and need much more CPU power to saturate the link.
So I don't think it's good idea to make rl(4) serve 8139C+.
perhaps, but re(4) doesn't work at the moment on this chipset, and i'd
rather have something which works, albeit a
Dinesh Nair [EMAIL PROTECTED] writes:
the symptoms remain the same, i.e. IP traffic doesn't flow at all,
though 'arp -an' does show the ethernet address of the other box
attempting to ping this.
'tcpdump -n -e -i re0' shows nothing?
have you tried disabling rx / tx checksum offloading?
On Mon, Aug 14, 2006 at 08:03:35PM +0800, Dinesh Nair wrote:
On 08/14/06 19:09 Pyun YongHyeon said the following:
really sucks and need much more CPU power to saturate the link.
So I don't think it's good idea to make rl(4) serve 8139C+.
perhaps, but re(4) doesn't work at the
On Monday 14 August 2006 02:46, Stanislav Sedov wrote:
Hi!
I'm trying to write kernel code where exceptions are unavoidable.
To clarify , I need to recover after GP (general protection) exception
on i386 cpu and return an error in that case.
Unfortunately, looking in trap.c kernel code I
On Saturday 12 August 2006 14:47, Mike Meyer wrote:
I just got a Prescott 2M core. While it's marketed as a P4, it's got
all the features of the Xeon Nocona core enabled (except for MP
support, of course): MMX, SSE, SSE2, SSE3, HT, EM64T, EIST and XD.
The question is whether or not the AMD64
On Mon, 14 Aug 2006 09:32:57 -0400
John Baldwin [EMAIL PROTECTED] mentioned:
You can make use of pcb_onfault to recover from a page fault, but that's
about it. Kernel code is expected to not generate exceptions. :)
Thanks a lot! I'll try it.
To clarify:
I've implemented driver to allow
In [EMAIL PROTECTED], John Baldwin [EMAIL PROTECTED] typed:
On Saturday 12 August 2006 14:47, Mike Meyer wrote:
I just got a Prescott 2M core. While it's marketed as a P4, it's got
all the features of the Xeon Nocona core enabled (except for MP
support, of course): MMX, SSE, SSE2, SSE3, HT,
Thanks. Was just checking.
On 8/14/06, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote:
Sean Bryant [EMAIL PROTECTED] writes:
I'm writing some cd buring software using burncd as a reference. I was
wondering if its possible to detect opening and closing of the doors.
Unfortunately, no. The drive
How about when media is loaded. I have a detection routine that'll ask
for media, but what about when any media is loaded? Is there some kind
of event or some way I can be notified.
On 8/14/06, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote:
Sean Bryant [EMAIL PROTECTED] writes:
I'm writing some
Stanislav Sedov wrote this message on Mon, Aug 14, 2006 at 19:47 +0600:
I've implemented driver to allow user-level code to read MSRs (Model
specific registers) (like linux's /dev/cpu/msr). It's required for
some programs like x86info.
As long as not all MSRs documented and reading/writing
On Monday 14 August 2006 09:47, Stanislav Sedov wrote:
On Mon, 14 Aug 2006 09:32:57 -0400
John Baldwin [EMAIL PROTECTED] mentioned:
You can make use of pcb_onfault to recover from a page fault, but that's
about it. Kernel code is expected to not generate exceptions. :)
Thanks a
On Mon, 14 Aug 2006 11:15:22 -0700
John-Mark Gurney [EMAIL PROTECTED] mentioned:
You should make a MD API for reading these out (if one doesn't already
exist) that handle the faulting for you, and then have your driver hook
into this api...
I had to do something similar for accessing PCI
Sean Bryant [EMAIL PROTECTED] writes:
How about when media is loaded. I have a detection routine that'll ask
for media, but what about when any media is loaded? Is there some kind
of event or some way I can be notified.
Sorry, no.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
Hi,
Is anyone here running 6.1 on Intel S5000PAL with dual-core Xeons?
--
Bob Bishop +44 (0)118 940 1243
[EMAIL PROTECTED] fax +44 (0)118 940 1295
___
freebsd-hackers@freebsd.org mailing list
Thanks anyway :(
On 8/14/06, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote:
Sean Bryant [EMAIL PROTECTED] writes:
How about when media is loaded. I have a detection routine that'll ask
for media, but what about when any media is loaded? Is there some kind
of event or some way I can be notified.
Stanislav Sedov wrote this message on Mon, Aug 14, 2006 at 23:12 +0600:
On Mon, 14 Aug 2006 11:15:22 -0700
John-Mark Gurney [EMAIL PROTECTED] mentioned:
You should make a MD API for reading these out (if one doesn't already
exist) that handle the faulting for you, and then have your
The section 4.11.1 Removable Media Status Notification feature set
of ATA/ATAPI-7 (http://t13.org/docs2004/d1532v1r4b-ATA-ATAPI-7.pdf) reads,
d) Host system periodically checks media status using the GET MEDIA
STATUS command to determine if any of the following events occurred:
- no media is
In message: [EMAIL PROTECTED]
[EMAIL PROTECTED] (Dag-Erling Smørgrav) writes:
: Sean Bryant [EMAIL PROTECTED] writes:
: How about when media is loaded. I have a detection routine that'll ask
: for media, but what about when any media is loaded? Is there some kind
: of event or some
One day, a friend told me that his program was 3 times slower under
FreeBSD 6.1 than under GNU/Linux (from Redhat 7.2 to Fedora Core 5).
I was astonished by the real repeatable performance difference on
AMD Athlon XP 2500+ (1.8GHz, 512KB L2 Cache).
After hacking, I found that the problem is
On Tue, Aug 15, 2006 at 07:10:47AM +0800, Intron wrote:
One day, a friend told me that his program was 3 times slower under
FreeBSD 6.1 than under GNU/Linux (from Redhat 7.2 to Fedora Core 5).
I was astonished by the real repeatable performance difference on
AMD Athlon XP 2500+ (1.8GHz, 512KB
Sorry for intrusion.
On Mon, 14 Aug 2006, Brooks Davis wrote:
On Tue, Aug 15, 2006 at 07:10:47AM +0800, Intron wrote:
One day, a friend told me that his program was 3 times slower under
FreeBSD 6.1 than under GNU/Linux (from Redhat 7.2 to Fedora Core 5).
I was astonished by the real
在 2006-08-15二的 02:38 +0300，Vladimir Kushnir写道：
On -CURENT amd64 (Athlon64 3000+, 512k L2 cache):
With jemalloc (without MY_MALLOS):
~/fdtd /usr/bin/time ./fdtd.FreeBSD 500 500 1000
...
116.34 real 113.69 user 0.00 sys
With MY_MALLOC:
~/fdtd /usr/bin/time ./fdtd.FreeBSD
I do not know what is the historical reason for program diff to follow
a symbolic link during the recursive diff (-r), but it seems not to be a
proper implementation.
If both compared directories contains a sym-link, which point to
a same file or directory, it obviously no need to compare it
37 matches
Mail list logo
