On Thu, Jan 28, 2010 at 4:11 PM, Oliver Schwartz Oliver.Schwartz at gmx.de
wrote:
Hi all,
On 28.01.2010 at 14:39 m. allan noah wrote:
I would do both- process ID combined with a hash of the device name,
I believe that would defeat the purpose. The whole point of the mutex is to
protect
Hi Allan,
Anyway, I've commited a hash function now. The new code should also
work on FreeBSD 8.0. If anyone can try it, I'd be much obliged.
I did not see any commit message. did you git push?
Err - yes, and it told me that it had pushed 4 or 5 objects. That was
my first git
Hi all,
On 26.01.2010, at 15:46, m. allan noah wrote:
Seems like an individual backend should not need to parse the device
string. Isn't there some other way to come up with a unique semaphore,
like process id?
the process id could be used, but it may fail theoretically. One
example is a
On Thu, Jan 28, 2010 at 6:51 AM, Oliver Schwartz Oliver.Schwartz at gmx.de
wrote:
Hi all,
On 26.01.2010, at 15:46, m. allan noah wrote:
Seems like an individual backend should not need to parse the device
string. Isn't there some other way to come up with a unique semaphore,
like process
Hi all,
On 28.01.2010 at 14:39 m. allan noah wrote:
I would do both- process ID combined with a hash of the device name,
I believe that would defeat the purpose. The whole point of the mutex is to
protect the USB device from simultaneous access from two processes, e.g. the
reader process and
Hi all,
On 25.01.2010, at 12:26, Torfinn Ingolfsen wrote:
In the meantime, another FreeBSD user found a way to fix it, it is
just a one-line patch:
http://lists.freebsd.org/pipermail/freebsd-usb/2010-January/
008172.html
With Andrew's patch, my scanner now works:
root at kg-v2#
On Tue, Jan 26, 2010 at 3:04 AM, Oliver Schwartz Oliver.Schwartz at
gmx.dewrote:
Hi all,
On 25.01.2010, at 12:26, Torfinn Ingolfsen wrote:
In the meantime, another FreeBSD user found a way to fix it, it is just a
one-line patch:
Seems like an individual backend should not need to parse the device
string. Isn't there some other way to come up with a unique semaphore,
like process id?
allan
On Tue, Jan 26, 2010 at 9:33 AM, Chris Bagwell chris at cnpbagwell.com wrote:
On Tue, Jan 26, 2010 at 3:04 AM, Oliver Schwartz
Hi,
On Sun, Jan 24, 2010 at 9:51 PM, Oliver Schwartz Oliver.Schwartz at
gmx.dewrote:
what does you snapscan.conf look like? If libusb is used, you mustn't use a
device entry such as /dev/... or libusb:/dev/ All that is needed is
the entry containing the vendor and product ID of your
Hi,
I have an old Agfa Snapscan 1212U scanner which have served me well for
years, using SANE under FreeBSD.
To make a long story short; FreeBSD 8.0-release came with a new usb stack,
and is using libusb.
And my scanner no longer works. Has anyone managed to get the snapscan
backend
10 matches
Mail list logo
