Not only legitimate, but required, depending on the class protocol.
Best regards,
--Terry
> -Original Message-
> From: tech-kern-ow...@netbsd.org [mailto:tech-kern-ow...@netbsd.org] On
> Behalf Of Greg Troxel
> Sent: Wednesday, December 30, 2015 17:36
> To: Brian Buhrow
> Cc: Nick Hudson
Brian Buhrow writes:
> To answer your question about whether there is a standard for
> generating these packets, it seems there is not. Linux expects you to use
> an ioctl() to generate the packet while FreeBSD expects you to send a write
> request with 0 bytes, as we do with the ugen(4)
hello greg. I've been trying to keep the noise on this thread to a
minimum, but it appears I mis-wrote about what happens when trying to
generate zero-length packets. The state of my re-worked ugen(4) is much
more stable and I have installed some additional diagnostics to determine
what is
Brian Buhrow writes:
> If I'm using ehci(4) and option DIAGNOSTIC is defined, I get a panic:
> "curlen == 0".
That's a bug. DIAGNOSTIC should only be checking assertions about
invariants that the code always maintains, not user input. So if there
is a requirement lower down in the stack
On Sun, Dec 27, 2015 at 02:26:36AM +, Taylor R Campbell wrote:
>
> This seems to have several functional changes in it:
>
> - Add cpu_rng(9) and its rndsource.
This is unusable and untestable without one or the other of the below:
> - Implement cpu_rng(9) on x86 using RDRAND/RDSEED for Inte
In article <20151230161150.GA29981@dstar>,
scole_mail wrote:
>The ia64 GENERIC kernel won't compile anymore:
>
>[snipped...]
># link GENERIC/netbsd
>/home/scole/nbsd/src/obj/tooldir.NetBSD-7.0.0_PATCH-i386/bin/ia64--netbsd-ld
>-Map netbsd.map --cref -T netbsd.ldscript -e start -X -o netbsd
On Wed, Dec 30, 2015 at 05:22:07PM +0100, Stephan wrote:
> Hi folks,
>
> to me it looks like files.kern in sys/kern is not included in the
> source tarballs of stable releases (e.g. netbsd-7). It is only visible
> in CVS under the MAIN tag.
The file is newer than the branch and not used there. Lo
Hi folks,
to me it looks like files.kern in sys/kern is not included in the
source tarballs of stable releases (e.g. netbsd-7). It is only visible
in CVS under the MAIN tag.
I´d like to continue some development based on the stable-7 source, so
I would expect files.kern to be there in order to in
hello. When I say sending zero-length transfers behave badly, I mean
diferent things happen depending on whether I'm using ehci(4), uhci(4) and
whether options DIAGNOSTIC is defined.
If I'm using ehci(4) and option DIAGNOSTIC is defined, I get a panic:
"curlen == 0".
If option DIA
The ia64 GENERIC kernel won't compile anymore:
[snipped...]
# link GENERIC/netbsd
/home/scole/nbsd/src/obj/tooldir.NetBSD-7.0.0_PATCH-i386/bin/ia64--netbsd-ld
-Map netbsd.map --cref -T netbsd.ldscript -e start -X -o netbsd
${SYSTEM_OBJ:N*swap*netbsd*} ${EXTRA_OBJ} vers.o swapnetbsd.o
acpi_
cherry@ wrote:
> Please find below a patch to remove .avail_(start|end) from
> struct vm_physseg
What's advantage of these changes?
Changing MD APIs could often cause botches on poor tierII ports..
> I couldn't find a reason for them to be used redundantly, but I may be
> wrong. Are there port
Hi Everyone,
Please find below a patch to remove .avail_(start|end) from
struct vm_physseg
I couldn't find a reason for them to be used redundantly, but I may be
wrong. Are there port specific uses for these ?
--
Cherry
diff -r 0b3902dbe274 sys/arch/acorn26/acorn26/pmap.c
--- a/sys/arch/acorn
> The destroyer would need the same logic to handle the case where there are no
> waiters.
Sorry, I should have been clearer. The (virtual) destroyer routine
checks for that condition:
if (port->kp_waiters > 0) {
port->kp_state = kp_deleted;
cv_broadcast(&port->kp_rdcv);
cv_broadcast(&port
Date: Tue, 29 Dec 2015 07:29:44 +0100
From: Stephan
Thanks for your explanation. There are 2 condvars for the object - as
far as I understand should one refcount be enough to make sure there
are no waiters left on both, correct?
Yes, that should be fine.
You don't even need to us
Date: Tue, 29 Dec 2015 10:41:39 +0100
From: Stephan
I think I found another approach. The destruction is now split in two parts:
1) The destroyer changes the state to destroyed and removes the object
from the global list.
2) Each waiter checks the state and waiters count of the
hello. For completeness, let me be more clear about what happens when
I attempt to send zero length packets to a USB device now that I've sorted
out the other issues.
With ehci(4) and options DIAGNOSTIC turned on, I get a
panic: curlen == 0.
Without options DIAGNOSTIC and ehci(
16 matches
Mail list logo
