Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Re: Openmoko Bug #2239: andy-tracking/bc49de906ce:
mach-gta02.c:1696: error: 'gta02_hdq_device' undeclared
(Openmoko Public Trac)
2. Re: Openmoko Bug #2232: unplugging with gadgetfs causes
panic: "softlockup: blocked tasks" (Openmoko Public Trac)
3. Openmoko Bug #2240: removing/reloading g_ether not working
(Openmoko Public Trac)
4. Re: Openmoko Bug #2235: Monochrome display on resume
(Openmoko Public Trac)
5. Re: Openmoko Bug #2235: Monochrome display on resume
(Openmoko Public Trac)
--- Begin Message ---
#2239: andy-tracking/bc49de906ce: mach-gta02.c:1696: error: 'gta02_hdq_device'
undeclared
--------------------------------+-------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution: fixed
Keywords: | Haspatch: 0
Blockedby: | Estimated:
Patchreview: | Blocking:
Reproducible: |
--------------------------------+-------------------------------------------
Changes (by andy):
* status: new => closed
* resolution: => fixed
Comment:
Thanks.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2239#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2232: unplugging with gadgetfs causes panic: "softlockup: blocked tasks"
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: in_testing
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by frankmpunkt):
I have a working example for an USB Gadget using GadgetFS on Openmoko.
Unfortunately it's not yet ready to be published. Did you check out the
patch from here https://docs.openmoko.org/trac/ticket/2206 ? It's the only
needed modification to the kernel source. I have modified the
configuration in usb.c for s3c2410_udc the following:
{{{
/* Samsung S3C24xx series, full speed only */
if (stat (DEVNAME = "s3c2410_udc", &statb) == 0) {
HIGHSPEED = 0;
device_desc.bcdDevice = __constant_cpu_to_le16 (0x0104),
fs_source_desc.bEndpointAddress = USB_DIR_IN | 2;
EP_IN_NAME = "ep2-bulk";
fs_sink_desc.bEndpointAddress = USB_DIR_OUT | 1;
EP_OUT_NAME = "ep1-bulk";
source_sink_intf.bNumEndpoints = 3;
fs_status_desc.bEndpointAddress = USB_DIR_IN | 3;
EP_STATUS_NAME = "ep3-bulk";
}
}}}
This works, although i am not quite sure if device_desc.bcdDevice is
correctly set. Hope this helps.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2232#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2240: removing/reloading g_ether not working
-------------------------+--------------------------------------------------
Reporter: frankmpunkt | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone:
Component: unknown | Version: unspecified
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-------------------------+--------------------------------------------------
The problem has already been recognized long ago:
https://docs.openmoko.org/trac/ticket/15 . This defect has been marked to
be fixed later. Now, two years later the same problem still occurs when
doing
{{{
ifconfig usb0 down
rmmod g_ether
modprobe g_ether
}}}
I'd like to switch between different USB Gadgets easily. But with this bug
it's even impossible to reboot properly.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2240>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2235: Monochrome display on resume
-----------------------------+----------------------------------------------
Reporter: zeroedout | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: display, resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by cedric.berger):
I also had this yesterday, for the first (and only) time.
After resume, display was only black and white.
This was with Qi and Android, Michael Trimarchi's latest version
(...v14.jffs2 and kernel-v12.bin -based on 2.6.29 I think-).
(Qi from 5 of ferbruary qi-s3c2442-master_c5c167a7f8f922b6.udfu)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2235#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2235: Monochrome display on resume
-----------------------------+----------------------------------------------
Reporter: zeroedout | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: display, resume
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by arhuaco):
FYI there is a relevant for this issue on the support ML:
http://lists.openmoko.org/pipermail/support/2009-February/004835.html
(start)
http://lists.openmoko.org/pipermail/support/2009-February/004843.html
(ref. to #2235)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2235#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog