This isn't specific to this thread, but does the charging not work out
of the box with berry_charge?
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still
On 11/23/07, Chris Frey [EMAIL PROTECTED] wrote:
I know the configuration exists, since the same code works when
the usb_storage module is not loaded.
I've always assumed that this conflict is a fundamental issue when
two programs try to access the same USB device (even if one is a kernel
If there are no devices with more than one functionally different
configuration, then why bother even checking?
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
On 11/23/07, Chris Frey [EMAIL PROTECTED] wrote:
I'm trying to determine if there is a way to read the current config
through libusb, in order to avoid calling set_configuration() if it is
already using #1.
Are there other configurations for the devices in question?
Perhaps one or both of the configurations supports both interfaces at
once. What is supported in Windows?
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
On 11/9/07, Chris Frey [EMAIL PROTECTED] wrote:
On Fri, Nov 09, 2007 at 10:11:24AM +0100, Niels De Vos wrote:
On 11/8/07, Chris Frey [EMAIL PROTECTED] wrote:
rmmod is not enough to prevent the conflict. You need to rename the
berry_charge module under /lib/modules before plugging in your
On 9/20/07, Chris Frey [EMAIL PROTECTED] wrote:
Hello all OpenSuSE users,
I know that Debian and Ubuntu use a system where devices are chowned
to the plugdev group for handheld devices. This is so users of that
group can use a device without being root.
I know that Fedora uses the
On 9/5/07, Chris Frey [EMAIL PROTECTED] wrote:
On Tue, Sep 04, 2007 at 10:01:41PM -0400, Simon Ruggier wrote:
Ok, I've fixed the inaccurate help string, removed the extra build
dep, and made the make dist warning into an error :)
Patch applied, thanks!
This change introduced something
On 9/4/07, Chris Frey [EMAIL PROTECTED] wrote:
Thanks for the patch! I've taken a look at it, and there are a couple
things I'm not keen on. If you send me a patch that addresses these
issues, I'll probably apply it. :-) You've fixed a number of configure
problems and made it more robust,
Here, test this out - everything should work the same, except that
there are --enable-gui and --enable-opensync flags that will configure
those directories and include them in all the recursive targets. I
also fixed all the Makefiles so that make dist generates a tarball
similar to the release
On 9/2/07, Chris Frey [EMAIL PROTECTED] wrote:
It can be automated with a script, and I could drop a build-all style
script in the root directory if this is a major problem.
How about building them conditionally with a configure flag like
--enable-opensync?
On 9/2/07, Chris Frey [EMAIL PROTECTED] wrote:
The advantage to keeping them separate is that they can be split into
separate source tarballs someday if needed. Not that it's likely, but
might be handy someday.
Are there real advantages to having things in one configure setup?
I don't
I don't know what the timeframe is, but the /sys//power/state
interfaces are deprecated anyway. Perhaps disabling it may fix this
problem somehow (or maybe prevent you from fixing it in userspace).
-
This SF.net email is
Here's the text they use:
CONFIG_PM_SYSFS_DEPRECATED:
The driver model started out with a sysfs file intended to provide
a userspace hook for device power management. This feature has never
worked very well, except for limited testing purposes, and so it will
be removed. It's not clear that a
Barry puts that there (I'm not commenting on how this affects your
problems though). In fact, you may be interested to know that you can
search for what package a file belongs to by running dpkg -S
/etc/udev/rules.d/10-blackberry.rules. You can even give part of a
filename and dpkg-query will
15 matches
Mail list logo
