GNU GRUB - Bugs: bug #26237, multiple problems with usb devices
You are not allowed to post comments on this tracker with your current authentication level.
bug #26237: multiple problems with usb devices
Submitter: | Oliver Henshaw <oliverhenshaw> | ||
Submitted: | Sun 19 Apr 2009 01:12:34 PM UTC | ||
Category: | None | Severity: | Major |
Priority: | 5 - Normal | Item Group: | None |
Status: | Fixed | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Closed | Release: | Bazaar - trunk |
Release: | r2127 | Reproducibility: | Every Time |
Planned Release: | None |
Jump to the original submission
Sun 14 Mar 2010 09:47:49 PM UTC, comment #7: |
Ales Nesrsta <starous> |
Sat 13 Mar 2010 10:08:44 PM UTC, comment #6: Hello. I found out the problem with grub_memalign. I'll apply the patch tomorrow. Some of the fixes can go directly in while other require investigation and perhaps even copyright assignment. Can you remove all gratuituous changes (like commenting out dprintfs, adding commented out code and change register names) and send patch in unified format (-u option in diff) to grub-devel@gnu.org? Porting code from linux is appropriate only if license is compatible and porting was approved by maintainer. Are perhaps interested in coding EHCI? |
Vladimir Serbinenko <phcoder> |
Fri 12 Mar 2010 10:38:32 PM UTC, comment #5: Hello,
|
Ales Nesrsta <starous> |
Fri 26 Feb 2010 04:07:12 PM UTC, comment #4: Hello,
|
Ales Nesrsta <starous> |
Wed 17 Jun 2009 01:22:50 PM UTC, comment #3: Has your patch that we committed recently fixed all this bugs? If it has please close this bugreport. Otherwise say which problems remain |
Vladimir Serbinenko <phcoder> |
Thu 07 May 2009 01:12:56 PM UTC, comment #2: With the attached patch, 'insmod ohci' no longer crashes. But
|
Oliver Henshaw <oliverhenshaw> |
Sun 19 Apr 2009 01:31:28 PM UTC, comment #1: I can boot with the stanza:
|
Oliver Henshaw <oliverhenshaw> |
Sun 19 Apr 2009 01:12:34 PM UTC, original submission:
I'm trying to use grub2 to boot from usb on a legacy system where the bios can't see the usb drive. The machine has (via) usb 1.1 ports attached to the motherboard and usb 2.0 ports on a (nec) pci card.
|
Oliver Henshaw <oliverhenshaw> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 15 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2010-10-16 | phcoder | Status | None | Fixed | |
Open/Closed | Open | Closed | |||
2010-03-13 | phcoder | Release | None | Bazaar - trunk | |
2010-03-12 | starous | Attached File | - | Added grub2-1.98~my_patched.20100312.patch, #19924 | |
2010-02-26 | starous | Attached File | - | Added lspci.txt, #19798 | |
Attached File | - | Added grub2_ohci_problem.txt, #19799 | |||
2009-05-07 | oliverhenshaw | Attached File | - | Added ohci_mouse.txt, #18110 | |
2009-05-07 | oliverhenshaw | Attached File | - | Added uchi_mouse_usb.txt, #18109 | |
2009-05-07 | oliverhenshaw | Attached File | - | Added usb-check-interface.patch, #18108 | |
2009-04-19 | oliverhenshaw | Attached File | - | Added uhci_usbms_usb.txt, #17959 | |
2009-04-19 | oliverhenshaw | Attached File | - | Added insmod_ohci.txt, #17958 | |
2009-04-19 | oliverhenshaw | Attached File | - | Added insmod_uhci_mouse.txt, #17957 | |
2009-04-19 | oliverhenshaw | Attached File | - | Added insmod_uhci_nomouse.txt, #17956 | |
2009-04-19 | oliverhenshaw | Attached File | - | Added my_pci.txt, #17954 | |
Attached File | - | Added my_usb.txt, #17955 |
Powered by Savane 3.13-caa5.
Corresponding source code
Hello,
there are answers.
OK, so I removed my workaround in HCCA allocation in patch.
I cleaned the code, shortly tested if it is still working, made the patch by "diff -urB" and sent it to grub-devel@gnu.org.
But as I did not participate on any Linux, GNU or another project until now, I am, for example, not sure if is it correct to do my patches according to grub2-1.98~experimental.20100120 source or if I should download some latest code tarball (if any)... Or if I should participate via CVS (I never used this tool and have no experiences...).
I never understand any license in details as I cannot be thinking as lawyer...
From my point of view, I did not port (copy) the code, I only used Linux developers experiences described in their notes, so I hope I don't need any approval.
I only shortly read part of Linux sources related to USB mass storage driver and I found in notes that there can be problem with USB mass storage devices if no Request Sense is performed after each command. By the way, I am not sure if I understand these notes in right way...
I don't know if lawyers have the same point of view...
I am personally not interested, as I do not have PC with EHCI which have no support for boot in BIOS.
But if You want to add EHCI module to GRUB2 or something like it and You need help, I can try to help You, I like programming on "device level".
But first please consider following facts and think over if I am suitable person for You:
1.
Improvement of GRUB2 OHCI module is my first try of participating in any free SW development. I only tried to solve this bug myself and when it looked that it is working, I send it to You mainly for review if it can be useful also for others.
2.
Till now I have no knowledges about UHCI and EHCI (as I had no knowledges about OHCI and USB MS approx. three weeks ago...).
This case was my first "meeting" with OHCI and USB mass storage devices specifications - I am not specialist, I downloaded specifications from www.usb.org, read them and try to compare it with GRUB2 code etc.
From SCSI side I have only very basic knowledges related to old SCSI2 draft document which I historically shortly read many years ago according to my experiments with building my own QIC02 SCSI miniport driver for Windows NT.
3.
I cannot do development systematically and fast due to my job, family and another, mostly non-predicate reasons. Sometimes I have some free time for such development, but often not. It can happen that I will be do nothing (nor responding) one, two, three weeks or more...
Ales