From: Justin Karneges <justin-qt@affinix.com>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] dtl1_cs suspend bug
Date: Tue, 23 Sep 2003 05:08:07 -0700 [thread overview]
Message-ID: <200309230508.07932.justin-qt@affinix.com> (raw)
In-Reply-To: <200309220408.04569.justin-qt@affinix.com>
Update...
I've spent way too many hours on this now, probably 12 in the last two days,
and still I have no solution. This is after crashing my Zaurus an
uncountable number of times. I'm about to give up, simply because I can't
waste away my time like this. What I wanted was to make this thing clean,
but instead I spent probably more time in hacking then I'll ever do in
ejecting and inserting of my Bluetooth card.
I don't think I want to see another info->link or mod_timer again in my life.
I hereby commend anyone who manages to do kernel development. Personally, I'd
like to start throwing things out the window.
Is it 5AM already?
-Justin
On Monday 22 September 2003 04:08 am, Justin Karneges wrote:
> Hi,
>
> I've started to try solving this one, but it is not easy for me since I
> know nothing about CardServices and what it does before/after issuing
> CS_EVENT_* events.
>
> I compared the dtl1_cs code to that of the orinoco_cs (wifi) driver, and I
> guess the handling is about the same. What could be wrong in dtl1_cs ?
>
> The fact that 'cardctl suspend' breaks the driver and 'cardctl eject ;
> cardctl insert' fixes it, I'm certain this can be solved in software.
> Surely there is a way that the driver can fully reset itself without it
> having to be done externally by cardmgr. I know that suspend/resume
> actions are supposed to be optimized versions of eject/insert, but since
> the current suspend/resume functions _don't_ work, we may as well do a full
> and slow reset instead. No sense in leaving it broken. Once someone comes
> along who understands how suspend/resume works, the driver can be
> optimized.
>
> Unfortunately, this isn't as easy as it appears on the surface. I tried a
> simple and dirty hack of making suspend perform the eject code and resume
> to perform the insert code (a cut and paste of just a few lines), but was
> unsuccessful.
>
> Clues please!
>
> -Justin
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-09-23 12:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 11:08 [Bluez-devel] dtl1_cs suspend bug Justin Karneges
2003-09-23 12:08 ` Justin Karneges [this message]
2003-09-23 12:19 ` Marcel Holtmann
2003-09-23 21:09 ` Justin Karneges
2003-09-23 21:37 ` Marcel Holtmann
2003-09-23 21:44 ` Justin Karneges
2003-09-23 22:17 ` Marcel Holtmann
2003-09-23 23:48 ` Justin Karneges
2003-09-24 1:35 ` Marcel Holtmann
2003-09-24 6:06 ` Justin Karneges
2003-09-24 9:36 ` Marcel Holtmann
2003-09-25 3:35 ` Justin Karneges
2003-09-23 12:49 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200309230508.07932.justin-qt@affinix.com \
--to=justin-qt@affinix.com \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox