Hello!
I've made the nsswitch + caching daemon project during the Google's
Summer of Code. There were some issues, though, in the first release of
the project.
Here is the second version of the patch:
http://www.rsu.ru/~bushman/nsswitch_cached/nss_cached.patch
It contains several new features,
i came across this message
http://lists.freebsd.org/pipermail/freebsd-current/2004-December/044395.html
and while it explains the use of bus_dmamap_sync, i'm still a little
confused on it's usage. i'm trying to port over a driver from freebsd 5.x
to freebsd 4.x, and it uses dma mapped
On 10/25/05 21:15 Dinesh Nair said the following:
the pseudo code for the read and write, called during an interrupt
cycle, are:
rx_func()
{
POSITION A
while(there_is_some_data) {
memcpy(somebuf, readbuf)
}
POSITION B
}
tx_func()
{
POSITION C
man bus_dma(9)
-Original Message-
From: Dinesh Nair [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 25, 2005 7:03 AM
To: Dinesh Nair
Cc: freebsd-hackers@freebsd.org
Subject: Re: correct use of bus_dmamap_sync
On 10/25/05 21:15 Dinesh Nair said the following:
the pseudo
On Tuesday 25 October 2005 09:15 am, Dinesh Nair wrote:
i came across this message
http://lists.freebsd.org/pipermail/freebsd-current/2004-December/044395.htm
l
and while it explains the use of bus_dmamap_sync, i'm still a little
confused on it's usage. i'm trying to port over a driver from
On Friday 21 October 2005 06:04 pm, Julian Elischer wrote:
John Baldwin wrote:
On Friday 21 October 2005 04:32 pm, David Schultz wrote:
On Fri, Oct 21, 2005, John Baldwin wrote:
On Friday 21 October 2005 09:13 am, nocool wrote:
freebsd-hackers�ï�¼Œhello
Question about 5.4 kernel source
At about the time of 10/24/2005 7:28 AM, victor cruceru stated the
following:
Daniel,
What is the OS version you are using when this is happening?
Did you try to update the libdevinfo (using cvsup for example) to a
newer version?
I think that under the original 5.4 it is a bug in devinfo(4)
On 10/26/05 01:27 John Baldwin said the following:
On Tuesday 25 October 2005 09:15 am, Dinesh Nair wrote:
(must i malloc space for them before passing them into those functions, or
will the call to bus_dmamem_alloc do it for me ?)
bus_dmamem_alloc() will do it for you.
thanx.
Probably
On 10/26/05 01:02 Singh, Vijay said the following:
man bus_dma(9)
thanx, but that doesn't exist on freebsd 4.x. though
http://www.freebsd.org/cgi/man.cgi?query=bus_dmamap_syncapropos=0sektion=0manpath=FreeBSD+5.4-stableformat=html
has it, it still applies only to 5.x.
--
Regards,
Hi Daniel,
Yes, this is the fix. And yes, I think that the bug was reported (at
least on a mailing list...)
BTW: I dare to suggest to fully upgrade your system to the latest
6.0, it is a huge step forward from 5.4. Before doing this you may
want to give it a try by booting from a CD and check
On Tuesday 25 October 2005 02:46 pm, Dinesh Nair wrote:
On 10/26/05 01:27 John Baldwin said the following:
On Tuesday 25 October 2005 09:15 am, Dinesh Nair wrote:
(must i malloc space for them before passing them into those functions,
or will the call to bus_dmamem_alloc do it for me ?)
On Tue, Oct 25, 2005 at 04:10:52PM -0400, John Baldwin wrote:
On Tuesday 25 October 2005 02:46 pm, Dinesh Nair wrote:
[...]
thus when you send data to your device, that is a WRITE operation (even
though your device is doing a DMA to read data), and when you get data
back from your
Apparently the original poster sent his question to me in private, then
sent it again to the mailing list right as I was responding in private.
Anyways, no need to continue to guess; if anyone has any questions, feel
free to ask.
Below is my response. Note that I edited it slightly to fix an
que onda hola estoy inetentando montar my memoria usbcon usbdevs -v
me aparece con el driver usb0
y cuando quiero montarla con mount_msdosfs /dev/usb1
/mnt/usb1
me mando un mensaje diciendo /dev/usb1 block device require
14 matches
Mail list logo
