All excellent points however We don't have an application that will
talk to a blackberry! We have an application that will talk to a
blackberry on the usb, we have one that will talk to one on bluetooth
and serial but, we don't have one that will talk to a blackberry. This
would be simple if R
>
> - usb.serial
> - usb.vendor_id
> - usb.product_id
>
> So it might be easier to do than it seems. Then again, I don't really
> know all that much about USB HAL, so perhaps these are just bogus settings.
Those fields are gathered from the usb data, so usb.vendor == 'Research
in Motion' or
Could you not have a userspace application interrogate the BB when
plugged in? After all, you do know it's a Blackberry (or at least a RIM
device) from the HAL logs sent by Edge.
There are also a bunch of identifiers that might identify the specific
device:
- usb.serial
- usb.vendor_id
- usb.
> Ah, now I think I understand better what you are thinking. You are
> detecting the BB properties from user space and stuffing the info back
> into the os (via hal) and using, or proposing to use, that info from
> other apps. Am I close?
Indeed, Usability by applications is what I'm thinking. Th
On Wed, Oct 8, 2008 at 11:59 AM, Martin Owens <[EMAIL PROTECTED]> wrote:
>> >>
>> >> udi =
>> >> '/org/freedesktop/Hal/devices/usb_device_fca_4_155FF3210780674CC49459D03AE08189ACFE3799_if1_scsi_host_scsi_device_lun0'
>> > snip
>> >> usb.version_bcd = 272 (0x110) (int)
>> >
>> > Which part of t
> >>
> >> udi =
> >> '/org/freedesktop/Hal/devices/usb_device_fca_4_155FF3210780674CC49459D03AE08189ACFE3799_if1_scsi_host_scsi_device_lun0'
> > snip
> >> usb.version_bcd = 272 (0x110) (int)
> >
> > Which part of that said it was an 8830? All I saw was generic devices.
>
> Is it important tha
On Wed, Oct 8, 2008 at 11:13 AM, Martin Owens <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-10-08 at 10:02 -0600, Brian Edginton wrote:
>> On Wed, Oct 8, 2008 at 9:51 AM, Martin Owens <[EMAIL PROTECTED]> wrote:
>> > The problem, is that it's not recognised in HAL. Most BlackBerries are
>> > recognised
On Wed, 2008-10-08 at 10:02 -0600, Brian Edginton wrote:
> On Wed, Oct 8, 2008 at 9:51 AM, Martin Owens <[EMAIL PROTECTED]> wrote:
> > The problem, is that it's not recognised in HAL. Most BlackBerries are
> > recognised as generic 0001/0004 or 0006 modes via usb_id. What you'd
> > need to do is wr
On Wed, Oct 8, 2008 at 9:51 AM, Martin Owens <[EMAIL PROTECTED]> wrote:
> The problem, is that it's not recognised in HAL. Most BlackBerries are
> recognised as generic 0001/0004 or 0006 modes via usb_id. What you'd
> need to do is write a HAL driver that can give something of a meaning to
> the de
The problem, is that it's not recognised in HAL. Most BlackBerries are
recognised as generic 0001/0004 or 0006 modes via usb_id. What you'd
need to do is write a HAL driver that can give something of a meaning to
the device other than the generic information available at the moment.
I wouldn't min
I agree with edge. I don't see much point in a kernel driver as it's
USB device and it's already recognized by the HAL. Perhaps a better
USB HAL driver, but a kernel driver seems like overkill and dangerous.
Chris.
Brian Edginton wrote:
> On Wed, Oct 8, 2008 at 7:03 AM, Martin Owens <[EMAIL
On Wed, Oct 8, 2008 at 7:03 AM, Martin Owens <[EMAIL PROTECTED]> wrote:
>
>> > I think it is best to start at the lowest level we can, and we may
>> > run into some roadblocks along the way. Especially the probe messages
>> > that are not well understood yet.
>
> Did you ever work out how to ident
> > I think it is best to start at the lowest level we can, and we may
> > run into some roadblocks along the way. Especially the probe messages
> > that are not well understood yet.
Did you ever work out how to identify a given BlackBerry device? having
good identification for devices is key if
On Wed, 2008-10-08 at 04:16 -0400, Chris Frey wrote:
> On Mon, Oct 06, 2008 at 08:06:04PM -0400, Rick Scott wrote:
> > I just noticed mention of a kernel driver in your TODO file. It just
> > happens that I'm looking at that now. My thought is to create a device
> > file for each "function". So for
On Mon, Oct 06, 2008 at 08:06:04PM -0400, Rick Scott wrote:
> I just noticed mention of a kernel driver in your TODO file. It just
> happens that I'm looking at that now. My thought is to create a device
> file for each "function". So for the first blackberry plugged in, you'd
> get bbdesktop0, bbm
Hi folks,
This is part shameless plug, and part explanation.
As you may know, the second annual Ontario Linux Fest is being held
in Toronto, Ontario this month on Saturday the 25th.
Also, as you may know, NetDirect, the company behind Barry, is very
heavily involved in the planning of this event
16 matches
Mail list logo
