Mike,
> I'm wanting to access the SocketCAN (Controller Area Network)
infrastructure from Mono.
> SocketCAN is part of the kernel networking infrastructure.
> It uses the standard sockets system calls with address family being
set to AF_CAN (29) and protocol family set to PF_CAN (29).
> Is there a
Hey,
If Carlos is getting his patch to serial.c ignored again, I'd also like to
resubmit my patch to the same file (raising the baud rate limit) to be ignored
at the same time :)
Thanks,
-Thad
-Original Message-
From: mono-devel-list-boun...@lists.ximian.com
[mailto:mono-devel-list-bo
pooled managers which would help give the desired
performance boost.
-Thad
-Original Message-
From: mono-devel-list-boun...@lists.ximian.com
[mailto:mono-devel-list-boun...@lists.ximian.com] On Behalf Of Thad
Thompson
Sent: Friday, January 08, 2010 4:23 PM
To: Miguel de Icaza
Cc: mono-devel
single internal buffer which would probably cause any consumer of
this class to crash and burn when run on Mono.
Regards,
-Thad
-Original Message-
From: Miguel de Icaza [mailto:mig...@novell.com]
Sent: Friday, January 08, 2010 4:06 PM
To: Thad Thompson
Cc: zvikag; mono-devel-list
Sorry if you misunderstood, the blog I linked to isn't mine - I was merely
referencing it an example of a managed buffer pool. There will almost certainly
still be some garbage collection going on but this can help reduce it. Also,
I'm not using the Begin/End calls unless the socket is going to
I feel your pain. I pulled a library across that did something similar,
and the large GC times had a visible, stop-the-world impact on latency.
Switching from garbage collected to managed buffers made a world of
difference. For more on this see:
http://msdn.microsoft.com/en-us/library/system.servi
Hi,
The native backend to the Socket implementation in Mono has fairly tight
checks on the protocol parameters handed to the low level socket. While
this catches problem early, it also prevents external extension of those
parameters. In my particular case, I'd like to access the Bluetooth
socket in
Hi,
I know this has been raised a few times in the past (bugs 332206,
334265, and 435127) but I've looked high and low for a workaround and
just can't seem to find it. Is there any way to catch, trap, log, crash,
or in any way be notified of an unhandled exception from a ThreadPool
thread? My apolo
Gerard,
Not sure that this will help, but I've built Mono for a couple of
different ARM processors using Scratchbox2 without too much pain. Below
I've attached the build steps from one of the more recent ones. You may
not need the CFLAGS="-DARM_FPU_FPA" directive.
-Thad
-
Hey Ya'll,
I'm all about performance, but there's more to Robert Jordan's point
than just the access time. As it's always been described and
implemented, a MemoryStream is an abstraction over an array of bytes.
GetBuffer is an escape interface which allows me to drop and resume that
abstraction whe
>So I think there should be a wrapper around BitConverter (and simular
functions), which simulates a little endian system.
That sounds nice, but you should take it up with Microsoft. They already
do deploy .NET on big-endian systems (Xbox 360). Moving applications
between platforms is fairly trans
I'd second that, and would like to help as well. On lightweight devices such as
netbooks the garbage collection latency becomes much more noticeable and a
production implementation of SGen would be very nice.
-Thad
-Original Message-
From: mono-devel-list-boun...@lists.ximian.com
[mai
12 matches
Mail list logo
