barry-devel — Development discussion mailing list

Re: [Barry-devel] USB Logs

[Toby G. <tob...@re...>]

On 23/12/11 02:01, Chris Frey wrote:
>> Are there any newer ways to get low-level logging information from running
>> loader that anyone is aware of?
> I'm afraid that USB-capture.txt is as complete as I know of. :-)

There are a couple of other windows tools (all XP only I think) listed 
at http://wiki.wireshark.org/Tools#USB_capture

I think I used SnoopyPro in the end.

If you've got (quite a lot of) money to spend then you could also go for 
a hardware USB analyzer, such as the LeCroy Advisor T3 
(http://www.lecroy.com/protocolanalyzer/protocoloverview.aspx?seriesid=280). 


If you've got a BeagleBoard (http://beagleboard.org/), or possibly other 
Linux hardware with a host and OTG USB port, then you might want to have 
a look at: http://elinux.org/BeagleBoard/GSoC/2010_Projects/USBSniffer

Regards,

Toby

Re: [Barry-devel] barrybackup and non-threaded sockets

[Chris F. <cd...@fo...>]

On Fri, Dec 23, 2011 at 11:52:05AM +0000, Christian Brassat wrote:
> Actually I was in a *real* hurry to get it working again, since it's a
> company phone. So I ended up using RIM's official Windows software. The
> phone has since gone back to it's assigned employee, but I can see if I
> can borrow another one for testing purposes, there's about 20 of them
> going around the company.

If you have the time, please do.  If you can get captures of working and
failing USB traces, that would be very helpful.

Thanks,
- Chris

Re: [Barry-devel] barrybackup and non-threaded sockets

[Christian B. <cr...@ma...>]

On Thu, Dec 22, 2011 at 08:51:41PM -0500, Chris Frey wrote:
> On Sat, Dec 17, 2011 at 03:46:08PM +0000, Christian Brassat wrote:
> > Hi,
> > 
> > I managed to compile Barry on CRUX, but when running barrybackup to
> > restore my Curve 9300, I'm running into problems. As soon as the program
> > starts up, I get an "Controller: requested mode not supported" error.
> > 
> > Full output of barrybackup -d can be found here:
> > http://paste.pocoo.org/show/521996
> > 
> > I think this is related to "Controller: Using non-threaded sockets",
> > since I get the same error when running btool -z, while everything is
> > fine with btool -Z.
> 
> Hi Christian,
> 
> Sorry for the delay... I've been sick for about a week.
> 
> Could you add a -v to the btool command line that succeeds and post that
> as well?
> 
> It is relatively easy to convert barrybackup to use threaded sockets too,
> but we might as well find out what the protocol issue is here, and fix
> that.  If you're in a hurry, though, let me know and I can post a patch
> for threaded-socket barrybackup.
> 
> Thanks,
> - Chris

Hey Chris,

Actually I was in a *real* hurry to get it working again, since it's a
company phone. So I ended up using RIM's official Windows software. The
phone has since gone back to it's assigned employee, but I can see if I
can borrow another one for testing purposes, there's about 20 of them
going around the company.

Christian

-- 
I used to have a signature. But it was too embarassed to be seen with me.

Re: [Barry-devel] USB Logs

[Chris F. <cd...@fo...>]

On Thu, Dec 22, 2011 at 03:39:24PM -0500, Jon Hylands wrote:
> Capturing: The RIM way
> ----------------------
> 
> It was reported on the mailing list that it is possible to add the
> following entries to the Windows Registry to cause RIM's software
> to create verbose logs in your temp directory.  Apparently this also
> enables sniffing the communication with the BlackBerry simulator.
> 
> Windows Registry Editor Version 5.00
> 
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RimUsb\Parameters]
> "FileDump"=dword:00000001
> "ServiceDebug"=dword:ffffffff

This is from a report from Robert Yaklin on the list:

http://www.mail-archive.com/bar...@li.../msg01750.html

Robert, do you remember where you found this information?  If it's documented
somewhere, maybe it's just a minor change.


> Does anyone know if this is still valid? I've tried it, and get nothing new
> in my Windows temp directory...

I haven't actually tried it myself, so I don't know if it is still valid.
Maybe newer desktop software drivers have changed since 2008/2009.


> Are there any newer ways to get low-level logging information from running
> loader that anyone is aware of?

I'm afraid that USB-capture.txt is as complete as I know of. :-)

- Chris

Re: [Barry-devel] barrybackup and non-threaded sockets

[Chris F. <cd...@fo...>]

On Sat, Dec 17, 2011 at 03:46:08PM +0000, Christian Brassat wrote:
> Hi,
> 
> I managed to compile Barry on CRUX, but when running barrybackup to
> restore my Curve 9300, I'm running into problems. As soon as the program
> starts up, I get an "Controller: requested mode not supported" error.
> 
> Full output of barrybackup -d can be found here:
> http://paste.pocoo.org/show/521996
> 
> I think this is related to "Controller: Using non-threaded sockets",
> since I get the same error when running btool -z, while everything is
> fine with btool -Z.

Hi Christian,

Sorry for the delay... I've been sick for about a week.

Could you add a -v to the btool command line that succeeds and post that
as well?

It is relatively easy to convert barrybackup to use threaded sockets too,
but we might as well find out what the protocol issue is here, and fix
that.  If you're in a hurry, though, let me know and I can post a patch
for threaded-socket barrybackup.

Thanks,
- Chris

[Barry-devel] USB Logs

[Jon H. <jo...@hu...>]

Hi everyone,

I have a question about USB logging. In the source tree somewhere there is
a file called USB-capture.txt, which includes the following at the end:

Capturing: The RIM way
----------------------

It was reported on the mailing list that it is possible to add the
following entries to the Windows Registry to cause RIM's software
to create verbose logs in your temp directory.  Apparently this also
enables sniffing the communication with the BlackBerry simulator.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RimUsb\Parameters]
"FileDump"=dword:00000001
"ServiceDebug"=dword:ffffffff



Does anyone know if this is still valid? I've tried it, and get nothing new
in my Windows temp directory...

Are there any newer ways to get low-level logging information from running
loader that anyone is aware of?

Thanks,
Jon

[Barry-devel] barrybackup and non-threaded sockets

[Christian B. <cr...@ma...>]

Hi,

I managed to compile Barry on CRUX, but when running barrybackup to
restore my Curve 9300, I'm running into problems. As soon as the program
starts up, I get an "Controller: requested mode not supported" error.

Full output of barrybackup -d can be found here:
http://paste.pocoo.org/show/521996

I think this is related to "Controller: Using non-threaded sockets",
since I get the same error when running btool -z, while everything is
fine with btool -Z.

Greetings, Christian

-- 
I used to have a signature. But it was too embarassed to be seen with me.

Re: [Barry-devel] Install problem

[Toby G. <tob...@re...>]

On 08/12/11 10:09, Chris Frey wrote:
> I'm assuming you downloaded the 0.17.x Barry sources?
>
> What distro are you using?
>
> Did you install the legacy libusb 0.1 API?

Also, do you have the output from running ./configure available, as well 
as the config.log file which running configure creates?

If you could attach both of those to an email then it'd be very useful 
in working out why it's having problems compiling.

Regards,

Toby

Re: [Barry-devel] Install problem

[Chris F. <cd...@fo...>]

On Wed, Dec 07, 2011 at 09:01:23PM -0600, br...@ab... wrote:
> downloaded source.  Ran...
> 
> ./configure
> ./make
> 
> 
> Received this error:
> 
> 
> usbwrap.h:176: error: ???usb_endpoint_descriptor??? was not declared in this scope
> usbwrap.h:176: error: template argument 2 is invalid
> usbwrap.h:176: error: template argument 4 is invalid
> usbwrap.h:181: error: ???usb_endpoint_descriptor??? was not declared in this scope
> usbwrap.h:181: error: template argument 2 is invalid
> usbwrap.h:181: error: template argument 4 is invalid
> usbwrap.h:203: error: field ???desc??? has incomplete type
> usbwrap.h:230: error: ???usb_config_descriptor??? does not name a type
> usbwrap.h:257: error: ???usb_device_descriptor??? does not name a type

Hi Brian,

I'm assuming you downloaded the 0.17.x Barry sources?

What distro are you using?

Did you install the legacy libusb 0.1 API?

- Chris

[Barry-devel] Install problem

[<br...@ab...>]

downloaded source.  Ran...

./configure
./make


Received this error:


usbwrap.h:176: error: ‘usb_endpoint_descriptor’ was not declared in this scope
usbwrap.h:176: error: template argument 2 is invalid
usbwrap.h:176: error: template argument 4 is invalid
usbwrap.h:181: error: ‘usb_endpoint_descriptor’ was not declared in this scope
usbwrap.h:181: error: template argument 2 is invalid
usbwrap.h:181: error: template argument 4 is invalid
usbwrap.h:203: error: field ‘desc’ has incomplete type
usbwrap.h:230: error: ‘usb_config_descriptor’ does not name a type
usbwrap.h:257: error: ‘usb_device_descriptor’ does not name a type


Any ideas?

Re: [Barry-devel] Need feedback: C++11 support

[Chris F. <cd...@fo...>]

On Tue, Nov 29, 2011 at 03:22:46PM +0000, Toby Gray wrote:
> For my desktop use of Barry I'm using Ubuntu 10.04, but I was planning 
> on upgrading to 12.04 when it's released (assuming it's the next LTS 
> Ubuntu). For all the cross compilation the compilers used by me are:
> QNX - gcc-4.4.2

Impressive that QNX is so recent.


> Android - gcc-4.4.3
> Linux ARM - gcc 4.1.2

Thanks!


> Overall I'd probably make my life easier to put off using C++11 features 
> for as long as possible, but it wouldn't be the end of the world if they 
> were used, especially if they made the development of Barry easier.

I'm thinking along the same lines. :-)

I guess Android is also in no hurry to upgrade either, since they don't
support everything as it is.

I hope that compiler support will sneak up on us before we're ready, and
then life will be smooth. :-)

- Chris

Re: [Barry-devel] Need feedback: C++11 support

[Toby G. <tob...@re...>]

Hi,

For my desktop use of Barry I'm using Ubuntu 10.04, but I was planning 
on upgrading to 12.04 when it's released (assuming it's the next LTS 
Ubuntu). For all the cross compilation the compilers used by me are:
QNX - gcc-4.4.2
Android - gcc-4.4.3
Linux ARM - gcc 4.1.2

However I'd be surprised if some of those version numbers haven't been 
increased by the end of next year. Even if they haven't then it should 
be possible to compile an updated version of GCC for all those 
platforms, which would at least give support for the syntax changes (but 
probably not the library or threading changes very easily).

Overall I'd probably make my life easier to put off using C++11 features 
for as long as possible, but it wouldn't be the end of the world if they 
were used, especially if they made the development of Barry easier.

Regards,

Toby

On 25/11/11 06:04, Chris Frey wrote:
> Hi list,
>
> I'm not in a hurry to move to C++11 support, but I do realize that it has
> some useful features that would make programming easier.  So someday
> Barry will likely use some C++11 features.
>
> The question is: when? :-)
>
> I base a lot of my work and "what's supported?" decisions on the latest
> release of Debian stable.  I often upgrade a few months late, too, when
> a new stable release of Debian comes out.
>
> I don't know what compiler will be in Wheezy when it becomes stable,
> but I assume it will have some support.
>
> Ubuntu 10.04 will likely still be one of the LTS candidates by that time,
> and it's C++11 support is limited, to my knowledge.
>
> So I doubt any C++11 stuff will creep into Barry in the next year.
>
> But after 2012?  That depends on the compilers you guys normally use.
> Please let me know what is in common use these days, and how long you
> plan to use them.
>
> Thanks!
> - Chris
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] OS7 devices - GetScreenshot not working

[Luca S. <me...@lu...>]

Chris,

amazing job! I have connected few OS7 devices and now the screenshot comes
crystal clear.

Thank you for your help.

Luca

On Fri, Nov 25, 2011 at 5:45 AM, Chris Frey <cd...@fo...> wrote:

> Hi Luca,
>
> I've updated the git tree with support for 32bit device screenshots.
>
> They seem to work with my testing here, based on the data you provided.
> Please give it a try and let me know.
>
> Thanks!
> - Chris
>
>
> On Tue, Nov 15, 2011 at 04:10:54PM +0000, Luca Sale wrote:
> > Hi Chris/Nicolas,
> >
> > thanks for the quick response.
> > I've attached the info requested.
> > the device attached was a torch 9860.
> >
> > Cheers,
> > Luca
> >
> >
> >
> > > On Mon, Nov 14, 2011 at 12:49 PM, Luca Sale <me...@lu...> wrote:
> > >
> > > On Mon, Nov 14, 2011 at 12:49:15PM +0000, Luca Sale wrote:
> > > > I recently got a new Torch 9860 and tried to get a screenshot but the
> > > > result was a not so pretty picture.
> > > > Have you guys tested "bjavaloader screenshot" with any of the new
> devices?
> > >
> > > Hi Luca,
> > >
> > > I don't have an OS7 device, so I'm not able to test Barry against it.
> > >
> > > But I've included a patch below which changed bjavaloader screenshot
> into a
> > > raw data capture.  If you could run it and send the resulting data
> file,
> > > I may be able to add support to Barry... it seems like it is an image
> format
> > > issue.
> > >
> > > Could you also include the following data captures:
> > >
> > >     btool -vl
> > >
> > >     bjavaloader deviceinfo
> > >
> > > Thanks!
> > > - Chris
> > >
> > >
> > > diff --git a/tools/bjavaloader.cc b/tools/bjavaloader.cc
> > > index 9e927ac..5dee60f 100644
> > > --- a/tools/bjavaloader.cc
> > > +++ b/tools/bjavaloader.cc
> > > @@ -186,8 +186,8 @@ void GetScreenshot(Barry::Mode::JavaLoader
> *javaloader, const char *filename)
> > >
> > >
> > >     // Convert to BMP format
> > > -   Data bitmap(-1, GetTotalBitmapSize(info));
> > > -   ScreenshotToBitmap(info, image, bitmap);
> > > +// Data bitmap(-1, GetTotalBitmapSize(info));
> > > +// ScreenshotToBitmap(info, image, bitmap);
> > >
> > >     // Write BMP file
> > >     FILE *fp = fopen(filename, "wb");
> > > @@ -196,7 +196,8 @@ void GetScreenshot(Barry::Mode::JavaLoader
> *javaloader, const char *filename)
> > >     }
> > >     AutoClose ac(fp);
> > >
> > > -   fwrite(bitmap.GetData(), bitmap.GetSize(), 1, fp);
> > > +   fwrite(&info, sizeof(info), 1, fp);
> > > +   fwrite(image.GetData(), image.GetSize(), 1, fp);
> > >  }
> > >
> > >  void SaveModule(Barry::Mode::JavaLoader *javaloader, const char
> *filename)
> > >
> > >
>
>
>
>
> >
> ------------------------------------------------------------------------------
> > RSA(R) Conference 2012
> > Save $700 by Nov 18
> > Register now
> > http://p.sf.net/sfu/rsa-sfdev2dev1
> > _______________________________________________
> > Barry-devel mailing list
> > Bar...@li...
> > https://lists.sourceforge.net/lists/listinfo/barry-devel
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel
>

Re: [Barry-devel] Barry & PlayBook

[Nicolas <pr...@fr...>]

Le vendredi 25 novembre 2011 à 05:17 -0500, Chris Frey a écrit :
> On Fri, Nov 25, 2011 at 10:57:51AM +0100, Nicolas wrote:
> > > > For the moment, I haven't succeed to run my tool from udev ; except if I
> > > > do : RUN+=/usr/sbin/bplaybook without filter...
> > > 
> > > Is the ProductID really 0020?  I don't have one, so I can't check this.
> > 
> > Yes 0x0020 for SCSI mode.
> > Then, 0x0011 for USBNET mode.
> 
> Interesting, because the ones you added in common.h seem different:
> 
> #define PRODUCT_RIM_PLAYBOOK_NETWORK    0x8011
> #define PRODUCT_RIM_PLAYBOOK_STORAGE    0x8020
> 
> 
> Am I missing something?

Sorry, my #define are OK :)

0x8020 for SCSI mode
and
0x8011 for USBNET mode

and so, I understand why my udev.rules doesn't work :)

So we have to fix the udev file ; and it works well.

thx

Nicolas

Re: [Barry-devel] Barry & PlayBook

[Chris F. <cd...@fo...>]

On Fri, Nov 25, 2011 at 10:57:51AM +0100, Nicolas wrote:
> > > For the moment, I haven't succeed to run my tool from udev ; except if I
> > > do : RUN+=/usr/sbin/bplaybook without filter...
> > 
> > Is the ProductID really 0020?  I don't have one, so I can't check this.
> 
> Yes 0x0020 for SCSI mode.
> Then, 0x0011 for USBNET mode.

Interesting, because the ones you added in common.h seem different:

#define PRODUCT_RIM_PLAYBOOK_NETWORK    0x8011
#define PRODUCT_RIM_PLAYBOOK_STORAGE    0x8020


Am I missing something?

- Chris

Re: [Barry-devel] Barry & PlayBook

[Nicolas <pr...@fr...>]

Le jeudi 24 novembre 2011 à 20:34 -0500, Chris Frey a écrit :
> On Fri, Nov 18, 2011 at 12:07:31AM +0100, Nicolas wrote:
> > You can find my barry commit about PlayBook :
> > 
> > http://repo.or.cz/w/barry/progweb.git/commit/130cd47bf9f2ac7ce7fd91dbba6b9cccf5d39b0e
> 
> Hi Nicolas,
> 
> Thanks for posting the code!
> 
> Unfortunately, this doesn't compile against libusb 1.0, so that needs to be
> fixed first.
> 
> The new ProbeResult m_class should be listed in its constructor too.
> 
> Also, I'm not sure the reset portion belongs in Probe.  Does the Playbook
> have a Database endpoint?
> 
> If there is no Database endpoint, maybe it makes more sense to make
> the ProbePlayBook class completely standalone, and not derived from
> Probe.  And call it ResetPlayBook or something similar.
> 
> It sounds like the SCSI PlayBook mode will hardly ever be used by Barry?
> Do we know what other modes exist?

It's a basic SCSI device only one mode.
The SCSI device provides only windows driver, and BlackBerry Desktop
Manager.
For Barry, it's unusefull.

After the USB net switch, you have a standard USB network device.

PlayBook doesn't offer "customize" interface as we can see with our
mobiles.

So, write a a new ProbePlayBook class standalone does sense.

RIM has chosen use only SAMBA connection with the playbook. And you
don't need computer to use this pad.

> > For the moment, I haven't succeed to run my tool from udev ; except if I
> > do : RUN+=/usr/sbin/bplaybook without filter...
> 
> Is the ProductID really 0020?  I don't have one, so I can't check this.

Yes 0x0020 for SCSI mode.
Then, 0x0011 for USBNET mode.

I'll had lsusb output for both modes in the barry doc sections.

> Also, you might need to restart udev when editing these things.  Hopefully
> udev is smart enough not to need a restart, but worth a try, since I've
> had issues in the past.
> 
> - Chris

Nicolas

[Barry-devel] Need feedback: C++11 support

[Chris F. <cd...@fo...>]

Hi list,

I'm not in a hurry to move to C++11 support, but I do realize that it has
some useful features that would make programming easier.  So someday
Barry will likely use some C++11 features.

The question is: when? :-)

I base a lot of my work and "what's supported?" decisions on the latest
release of Debian stable.  I often upgrade a few months late, too, when
a new stable release of Debian comes out.

I don't know what compiler will be in Wheezy when it becomes stable,
but I assume it will have some support.

Ubuntu 10.04 will likely still be one of the LTS candidates by that time,
and it's C++11 support is limited, to my knowledge.

So I doubt any C++11 stuff will creep into Barry in the next year.

But after 2012?  That depends on the compilers you guys normally use.
Please let me know what is in common use these days, and how long you
plan to use them.

Thanks!
- Chris

Re: [Barry-devel] OS7 devices - GetScreenshot not working

[Chris F. <cd...@fo...>]

Hi Luca,

I've updated the git tree with support for 32bit device screenshots.

They seem to work with my testing here, based on the data you provided.
Please give it a try and let me know.

Thanks!
- Chris


On Tue, Nov 15, 2011 at 04:10:54PM +0000, Luca Sale wrote:
> Hi Chris/Nicolas,
> 
> thanks for the quick response.
> I've attached the info requested.
> the device attached was a torch 9860.
> 
> Cheers,
> Luca
> 
> 
> 
> > On Mon, Nov 14, 2011 at 12:49 PM, Luca Sale <me...@lu...> wrote:
> >
> > On Mon, Nov 14, 2011 at 12:49:15PM +0000, Luca Sale wrote:
> > > I recently got a new Torch 9860 and tried to get a screenshot but the
> > > result was a not so pretty picture.
> > > Have you guys tested "bjavaloader screenshot" with any of the new devices?
> >
> > Hi Luca,
> >
> > I don't have an OS7 device, so I'm not able to test Barry against it.
> >
> > But I've included a patch below which changed bjavaloader screenshot into a
> > raw data capture.  If you could run it and send the resulting data file,
> > I may be able to add support to Barry... it seems like it is an image format
> > issue.
> >
> > Could you also include the following data captures:
> >
> > 	btool -vl
> >
> > 	bjavaloader deviceinfo
> >
> > Thanks!
> > - Chris
> >
> >
> > diff --git a/tools/bjavaloader.cc b/tools/bjavaloader.cc
> > index 9e927ac..5dee60f 100644
> > --- a/tools/bjavaloader.cc
> > +++ b/tools/bjavaloader.cc
> > @@ -186,8 +186,8 @@ void GetScreenshot(Barry::Mode::JavaLoader *javaloader, const char *filename)
> >
> >
> >  	// Convert to BMP format
> > -	Data bitmap(-1, GetTotalBitmapSize(info));
> > -	ScreenshotToBitmap(info, image, bitmap);
> > +//	Data bitmap(-1, GetTotalBitmapSize(info));
> > +//	ScreenshotToBitmap(info, image, bitmap);
> >
> >  	// Write BMP file
> >  	FILE *fp = fopen(filename, "wb");
> > @@ -196,7 +196,8 @@ void GetScreenshot(Barry::Mode::JavaLoader *javaloader, const char *filename)
> >  	}
> >  	AutoClose ac(fp);
> >
> > -	fwrite(bitmap.GetData(), bitmap.GetSize(), 1, fp);
> > +	fwrite(&info, sizeof(info), 1, fp);
> > +	fwrite(image.GetData(), image.GetSize(), 1, fp);
> >  }
> >
> >  void SaveModule(Barry::Mode::JavaLoader *javaloader, const char *filename)
> >
> >




> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Barry-devel mailing list
> Bar...@li...
> https://lists.sourceforge.net/lists/listinfo/barry-devel

Re: [Barry-devel] Barry & PlayBook

[Chris F. <cd...@fo...>]

On Thu, Nov 24, 2011 at 08:34:00PM -0500, Chris Frey wrote:
> Unfortunately, this doesn't compile against libusb 1.0, so that needs to be
> fixed first.

I think the libusb 1.0 API is libusb_kernel_driver_active() instead of
the libusb 0.1 call of usb_get_driver_np().

I've merged in some of the changes from your patch, with fixes.

Could you give it a try with libusb 1.0 and make sure that it works with
your Playbook?  You'll have to add the playbook part of your patch on
top of what's there to test.

Thanks!
- Chris

Re: [Barry-devel] Barry & PlayBook

[Chris F. <cd...@fo...>]

On Fri, Nov 18, 2011 at 12:07:31AM +0100, Nicolas wrote:
> You can find my barry commit about PlayBook :
> 
> http://repo.or.cz/w/barry/progweb.git/commit/130cd47bf9f2ac7ce7fd91dbba6b9cccf5d39b0e

Hi Nicolas,

Thanks for posting the code!

Unfortunately, this doesn't compile against libusb 1.0, so that needs to be
fixed first.

The new ProbeResult m_class should be listed in its constructor too.

Also, I'm not sure the reset portion belongs in Probe.  Does the Playbook
have a Database endpoint?

If there is no Database endpoint, maybe it makes more sense to make
the ProbePlayBook class completely standalone, and not derived from
Probe.  And call it ResetPlayBook or something similar.

It sounds like the SCSI PlayBook mode will hardly ever be used by Barry?
Do we know what other modes exist?


> For the moment, I haven't succeed to run my tool from udev ; except if I
> do : RUN+=/usr/sbin/bplaybook without filter...

Is the ProductID really 0020?  I don't have one, so I can't check this.

Also, you might need to restart udev when editing these things.  Hopefully
udev is smart enough not to need a restart, but worth a try, since I've
had issues in the past.

- Chris

Re: [Barry-devel] OS7 devices - GetScreenshot not working

[Chris F. <cd...@fo...>]

On Tue, Nov 22, 2011 at 02:19:17PM +0000, Luca Sale wrote:
> Hey Guys,
> 
> have you had the chance to have a look at the attachments I sent on the
> 15th?
> is the raw image being fetched from the OS7 device properly?

Hi Luca,

Sorry, I haven't gotten to it yet.  I hope to get to it this week, though,
and I'll let you know my progress whether I have success or not.

Stay tuned... thanks for your quick data capture!

- Chris

Re: [Barry-devel] OS7 devices - GetScreenshot not working

[Luca S. <me...@lu...>]

Hey Guys,

have you had the chance to have a look at the attachments I sent on the
15th?
is the raw image being fetched from the OS7 device properly?

Let me know if you require anything else.

Cheers,
Luca

Re: [Barry-devel] Barry & PlayBook

[Nicolas <pr...@fr...>]

Le mardi 15 novembre 2011 à 15:42 -0500, Chris Frey a écrit :
> On Tue, Nov 15, 2011 at 09:15:59PM +0100, Nicolas wrote:
> > How can I integrate this in Barry project ? Are you interested in this
> > mini application ? 
> 
> Absolutely! :-)
> 
> 
> > The easy way is only create a new directory "playbook" with sources. The
> > sources are independant of barry project.
> > 
> > Or do you prefer that I use Probe class and your USB wrapper ?
> 
> Could I take a look at the source?  It would be nice if it took advantage
> of Barry's ability to use both libusb libraries, but I don't know how
> feasible that is without seeing the source.

Hi Chri,

You can find my barry commit about PlayBook :

http://repo.or.cz/w/barry/progweb.git/commit/130cd47bf9f2ac7ce7fd91dbba6b9cccf5d39b0e

For the moment, I haven't succeed to run my tool from udev ; except if I
do : RUN+=/usr/sbin/bplaybook without filter...

Regards,

Nicolas

Re: [Barry-devel] Barry & PlayBook

[Chris F. <cd...@fo...>]

On Tue, Nov 15, 2011 at 09:15:59PM +0100, Nicolas wrote:
> How can I integrate this in Barry project ? Are you interested in this
> mini application ? 

Absolutely! :-)


> The easy way is only create a new directory "playbook" with sources. The
> sources are independant of barry project.
> 
> Or do you prefer that I use Probe class and your USB wrapper ?

Could I take a look at the source?  It would be nice if it took advantage
of Barry's ability to use both libusb libraries, but I don't know how
feasible that is without seeing the source.

- Chris

[Barry-devel] Barry & PlayBook

[Nicolas <pr...@fr...>]

Hi Chris and barry users,

I have bought a PlayBook (very nice tab).

PlayBook runs on QNX (or BBX for RIM).

The new mobiles will be also under BBX. I don't know if the USB protocol
(for sync, javaloader...) will adapt to BBX devices.

For the moment, the playbook haven't this feature.

Nevertheless, the PlayBook provides an USB interface, but not a
mass-storage interface.

The PlayBook USB interface simulates a network interface with a DHCP
server ; so your computer does a dhcp request, and creates a USB network
interface :
usb0      Link encap:Ethernet  HWaddr 72:d4:f2:78:ea:2c  
          inet adr:169.254.93.26  Bcast:169.254.93.27
Masque:255.255.255.252
          adr inet6: fe80::70d4:f2ff:fe78:ea2c/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:2942 (2.8 KiB)  TX bytes:10048 (9.8 KiB)

Then, you can access to PlayBook data from netbios protocol (with a SMB
client).

It works great...

But...

You have to set the network sharing mode on the PlayBook device :
a) Automatic mode
b) Windows
c) MAC
(and of course, not Linux !)

After usbsnooping... 
a) I don't know how to the playbook determines windows or mac... but it
isn't important :/
b) Emulates a SCSI storage with autorun to install a Windows driver.
The windows driver permits to switch the SCSI interface to network
interface
c) directly network interface (the USB network has to be natif on MAC)


So, set "MAC mode" for a Linux users is disapointing !


I have written a little driver to be able to work in "Automatic mode" or
"windows mode" (of course, it works also in MAC mode).

My userspace driver uses libusb (as barry). My app is so launch by udev
to switch SCSI to USBNET mode.

It works :)


How can I integrate this in Barry project ? Are you interested in this
mini application ? 
The easy way is only create a new directory "playbook" with sources. The
sources are independant of barry project.

Or do you prefer that I use Probe class and your USB wrapper ?

In this case, I have to change a bit the API to permit to filter on
device type : "mobile" or "playbook" (bbos or bbx)


Regards,

Nicolas