From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [Patch] USB hot-plugging support - usb branch
Date: Wed, 28 Jul 2010 17:55:02 +0300 [thread overview]
Message-ID: <4C5044C6.1060807@gmail.com> (raw)
In-Reply-To: <1279995332.4817.135.camel@pracovna>
[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]
On 07/24/2010 09:15 PM, Aleš Nesrsta wrote:
> Yes, it is one of possible and simplest ways... In first try we can
> increase number of EDs to approx. 255 + 1 control and 2*255 bulk EDs per
> OHCI/UHCI controller. (We need one control ED and two bulk EDs per one
> mass storage device plus one control zero ED for new connected device.)
> I.e. currently we can simply change in ohci.c:
> #define GRUB_OHCI_CTRL_EDS 256
> #define GRUB_OHCI_BULK_EDS 510
> and it should be enough...
>
> But it will be better to finally implement also some ED de-allocating in
> OHCI. I want to try to implement device-port information into usbdevice
> structure and together with it add de-allocating of OHCI EDs - see
> below.
>
>
Allocating and deallocating is relatively expensive to maintain. Usually
the benefit is far greater. In this case it's only about saving few KB
of memory. It's simply not worth it. Don't bother about it.
>> ...
>>
>>> There is missing handling of disconnected devices. For this we will
>>>
>> need
>>
>>> to know on which port which device is attached - it is currently not
>>> known
>>>
>> But it can be easily stored in usbdevice structure.
>>
> I have similar idea, do you mean this structure ?
>
> usb.h: struct grub_usb_device
>
> (I am thinking how to simply implement recursive structure of USB bus -
> root hub, hubs, devices on hubs at any level... Exists some similar
> problems/structures somewhere in GRUB (to use the same or similar
> implementation or, at least, to be inspired) ?)
>
>
I would use linked lists.
> But as I wrote in another today's e-mail to jonatan perry, I will
> probably too busy in next weeks/months, so it may take some longer
> time... ( BTW - What do you mean about EHCI driver and its priority in
> GRUB development ? But it is probably theme for another mail thread...)
>
>
EHCI is important.
> Regards
> Ales
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2010-07-28 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 9:21 [Patch] Simple USB hub support Aleš Nesrsta
2010-06-20 18:25 ` richardvoigt
2010-06-21 19:56 ` Aleš Nesrsta
2010-06-28 16:44 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-07-05 17:11 ` Aleš Nesrsta
2010-07-05 23:59 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-07-06 17:14 ` Aleš Nesrsta
2010-07-06 17:23 ` Colin Watson
2010-07-06 23:06 ` [Patch] USB hot-plugging support - usb branch Aleš Nesrsta
2010-07-08 21:11 ` Aleš Nesrsta
2010-07-17 11:34 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-07-17 11:38 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-07-24 18:15 ` Aleš Nesrsta
2010-07-28 14:55 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=4C5044C6.1060807@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.