On 05/02/2011, at 16:11, Daniel O'Connor wrote:
>> The correct solution is 'USE_LIBUSB=yes' with relevant magic in bsd.port.mk
>> Unfortunately this is unlikely to occur because it's only needed for 7.x
>> which will be dying within the next few years.
>
> USE_LIBUSB= would be nice, I will see if
On Sun, 6 Feb 2011, Benjamin wrote:
The Olimex is a programmer for AVR microcontrollers. It is apparently an FTDI
device and works under Linux. The product page at
http://www.olimex.com/dev/avr-isp500.html provides source code for a Linux
FTDI kernel module.
I have the looked through the Lin
The Olimex is a programmer for AVR microcontrollers. It is apparently an
FTDI device and works under Linux. The product page at
http://www.olimex.com/dev/avr-isp500.html provides source code for a
Linux FTDI kernel module.
I have the looked through the Linux FTDI driver source code and have
e
On Sat, 05 Feb 2011 11:28:31 -0500
Donald Allen wrote:
> On Sat, Feb 5, 2011 at 10:28 AM, Hans Petter Selasky wrote:
>
> > On Saturday 05 February 2011 16:18:56 Donald Allen wrote:
> > > Does whoever is responsible for CAM/SCSI
> > > know about this and do you know if there are plans to fix it?
On 2/5/11 8:28 AM, Donald Allen wrote:
On Sat, Feb 5, 2011 at 10:28 AM, Hans Petter Selaskywrote:
On Saturday 05 February 2011 16:18:56 Donald Allen wrote:
Does whoever is responsible for CAM/SCSI
know about this and do you know if there are plans to fix it? What is the
point of "supporting" U
>
> Hans Petter,
> Could the USB mass storage layer not refuse to pass down some commands
> and just return the proscribed error?
Yes, that's what I'm thinking would be the simplest solution. I just need an
overview which SCSI commands we should pass and not pass. Do you have an idea?
--hps
_
On Sat, Feb 5, 2011 at 10:28 AM, Hans Petter Selasky wrote:
> On Saturday 05 February 2011 16:18:56 Donald Allen wrote:
> > Does whoever is responsible for CAM/SCSI
> > know about this and do you know if there are plans to fix it? What is the
> > point of "supporting" USB devices (and we aren't ta
On Saturday 05 February 2011 16:18:56 Donald Allen wrote:
> Does whoever is responsible for CAM/SCSI
> know about this and do you know if there are plans to fix it? What is the
> point of "supporting" USB devices (and we aren't talking about an odd-ball
> device here; these are USB disks), when the
On Sat, Feb 5, 2011 at 9:34 AM, Hans Petter Selasky wrote:
> On Saturday 05 February 2011 14:27:56 Donald Allen wrote:
> > I've discussed problems with FreeBSD and usb sata drives on this list
> > in the past (as recently as last September), and have given up on
> > FreeBSD as a result of the usb
On Saturday 05 February 2011 14:27:56 Donald Allen wrote:
> I've discussed problems with FreeBSD and usb sata drives on this list
> in the past (as recently as last September), and have given up on
> FreeBSD as a result of the usb disk problems (I do my backups with usb
> drives) and other usb-rela
I've discussed problems with FreeBSD and usb sata drives on this list
in the past (as recently as last September), and have given up on
FreeBSD as a result of the usb disk problems (I do my backups with usb
drives) and other usb-related issues. But I've now replaced the usb
enclosures I was using a
On Sat, Feb 05, 2011 at 04:11:08PM +1030, Daniel O'Connor wrote:
>
> On 05/02/2011, at 16:01, Peter Jeremy wrote:
> >> On 07/01/2010, at 14:54, Daniel O'Connor wrote:
> >>> One problem is that ports don't know which version to use, it would be
> >>> nice
> >>> if they could just depend on devel/
12 matches
Mail list logo
