* Support for 0489:e031 Foxconn / Hon Hai
@ 2011-06-01 11:48 thilo
2011-06-02 1:03 ` Marcel Holtmann
0 siblings, 1 reply; 9+ messages in thread
From: thilo @ 2011-06-01 11:48 UTC (permalink / raw)
To: linux-bluetooth
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
Hey,
I got a new laptop and as usual new hardware has devices which aren't supported.
In this case, it is the bluetooth adapter of the Fujitsu Lifebook E751.
I have attached the lsusb -v output corresponding the adapter.
Can someone please tell me, which information are also needed so support can be implemented?
Should I contact Foxconn (or Broadcom) if they have a public spec?
As it is a internal usb bluetooth adapter might it be enough to add the ID to btusb.c? (didn't work so far ;) )
Any other hints?
Ciao
Thilo
[-- Attachment #2: lsusb.verbose.txt --]
[-- Type: text/plain, Size: 10923 bytes --]
Bus 002 Device 005: ID 0489:e031 Foxconn / Hon Hai
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 1
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0489 Foxconn / Hon Hai
idProduct 0xe031
bcdDevice 1.12
iManufacturer 1 Broadcom Corp
iProduct 2 BCM20702A0
iSerial 3 EC55F9EADE09
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 218
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 0
Device Firmware Upgrade Interface Descriptor:
bLength 9
bDescriptorType 33
bmAttributes 5
Will Not Detach
Manifestation Tolerant
Upload Unsupported
Download Supported
wDetachTimeout 5000 milliseconds
wTransferSize 64 bytes
bcdDFUVersion 1.10
Device Status: 0x0001
Self Powered
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Support for 0489:e031 Foxconn / Hon Hai
2011-06-01 11:48 thilo
@ 2011-06-02 1:03 ` Marcel Holtmann
2011-06-02 7:23 ` Thilo Cestonaro
0 siblings, 1 reply; 9+ messages in thread
From: Marcel Holtmann @ 2011-06-02 1:03 UTC (permalink / raw)
To: thilo; +Cc: linux-bluetooth
Hi Thilo,
> I got a new laptop and as usual new hardware has devices which aren't supported.
> In this case, it is the bluetooth adapter of the Fujitsu Lifebook E751.
>
> I have attached the lsusb -v output corresponding the adapter.
>
> Can someone please tell me, which information are also needed so support can be implemented?
>
> Should I contact Foxconn (or Broadcom) if they have a public spec?
>
> As it is a internal usb bluetooth adapter might it be enough to add the ID to btusb.c? (didn't work so far ;) )
what about the usb-devices.sh script output or /proc/bus/usb/devices
content for this adatper.
Regards
Marcel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Support for 0489:e031 Foxconn / Hon Hai
2011-06-02 1:03 ` Marcel Holtmann
@ 2011-06-02 7:23 ` Thilo Cestonaro
0 siblings, 0 replies; 9+ messages in thread
From: Thilo Cestonaro @ 2011-06-02 7:23 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: linux-bluetooth
Hey Marcel,
>> I got a new laptop and as usual new hardware has devices which aren't =
supported.
>> In this case, it is the bluetooth adapter of the Fujitsu Lifebook =
E751.=20
>>=20
>> I have attached the lsusb -v output corresponding the adapter.
>>=20
>> Can someone please tell me, which information are also needed so =
support can be implemented?
>>=20
>> Should I contact Foxconn (or Broadcom) if they have a public spec?
>>=20
>> As it is a internal usb bluetooth adapter might it be enough to add =
the ID to btusb.c? (didn't work so far ;) )
>=20
> what about the usb-devices.sh script output or /proc/bus/usb/devices
> content for this adatper.
I currently have no access to my laptop, as it is at work. I'll have a =
look for the devices stuff on monday.
Ciao
Thilo=
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Support for 0489:e031 Foxconn / Hon Hai
@ 2011-06-08 13:33 thilo
2011-06-09 10:21 ` Marcel Holtmann
0 siblings, 1 reply; 9+ messages in thread
From: thilo @ 2011-06-08 13:33 UTC (permalink / raw)
To: linux-bluetooth
Hey again,
This does look better now, right?
T: Bus=02 Lev=02 Prnt=02 Port=03 Cnt=03 Dev#= 11 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0489 ProdID=e031 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM20702A0
S: SerialNumber=EC55F9EADE09
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
but the two last lines still have no driver. Is this a problem?
Here is the output of hciconfig hci0 -a:
$ hciconfig hci0 -a
hci0: Type: BR/EDR Bus: USB
BD Address: EC:55:F9:EA:DE:09 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:5947 acl:0 sco:0 events:198 errors:0
TX bytes:1986 acl:0 sco:0 commands:117 errors:0
Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'abg4858n-lnx'
Class: 0x4a0100
Service Classes: Networking, Capturing, Telephony
Device Class: Computer, Uncategorized
HCI Version: 4.0 (0x6) Revision: 0x0
LMP Version: 4.0 (0x6) Subversion: 0x2118
Manufacturer: Broadcom Corporation (15)
Looks ok isn't it?
But I can't add any devices. When I search for devices VERY long, I can find one or two. But only devices which I can't pair with.
e.g. I never found my headset, altought it is in pairing mode when I start searching.
During search, hcidump -v shows only this:
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
so no problem here too.
Any suggestions what I could try next? Anything which could give me informations whats going wrong here?
Ciao
Thilo
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Support for 0489:e031 Foxconn / Hon Hai
2011-06-08 13:33 thilo
@ 2011-06-09 10:21 ` Marcel Holtmann
0 siblings, 0 replies; 9+ messages in thread
From: Marcel Holtmann @ 2011-06-09 10:21 UTC (permalink / raw)
To: thilo; +Cc: linux-bluetooth
Hi Thilo,
> This does look better now, right?
> T: Bus=02 Lev=02 Prnt=02 Port=03 Cnt=03 Dev#= 11 Spd=12 MxCh= 0
> D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=0489 ProdID=e031 Rev=01.12
> S: Manufacturer=Broadcom Corp
> S: Product=BCM20702A0
> S: SerialNumber=EC55F9EADE09
> C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
> I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
> I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
> I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>
> but the two last lines still have no driver. Is this a problem?
that is fine. They are some Broadcom specific endpoint and the firmware
update endpoint. No need to have the btusb driver attach to it. It only
uses the first two endpoints.
> Here is the output of hciconfig hci0 -a:
> $ hciconfig hci0 -a
> hci0: Type: BR/EDR Bus: USB
> BD Address: EC:55:F9:EA:DE:09 ACL MTU: 1021:8 SCO MTU: 64:1
> UP RUNNING PSCAN ISCAN
> RX bytes:5947 acl:0 sco:0 events:198 errors:0
> TX bytes:1986 acl:0 sco:0 commands:117 errors:0
> Features: 0xff 0xff 0x8f 0xfe 0xdb 0xff 0x7b 0x87
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'abg4858n-lnx'
> Class: 0x4a0100
> Service Classes: Networking, Capturing, Telephony
> Device Class: Computer, Uncategorized
> HCI Version: 4.0 (0x6) Revision: 0x0
> LMP Version: 4.0 (0x6) Subversion: 0x2118
> Manufacturer: Broadcom Corporation (15)
>
> Looks ok isn't it?
Yes, and getting a nice Low-Energy capable dongle is great. Where did
you get this from? I like to get a bunch of these for testing.
> But I can't add any devices. When I search for devices VERY long, I can find one or two. But only devices which I can't pair with.
> e.g. I never found my headset, altought it is in pairing mode when I start searching.
>
> During search, hcidump -v shows only this:
> > HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
> > HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
> > HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
> > HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
> > HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
> > HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
> > HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
> > HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
> > HCI Event: Inquiry Complete (0x01) plen 1
> status 0x00
>
> so no problem here too.
>
> Any suggestions what I could try next? Anything which could give me informations whats going wrong here?
Maybe the antenna is kinda wrongly calibrated, but I can't tell any
details here. That is hardware specific.
Regards
Marcel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Support for 0489:e031 Foxconn / Hon Hai
@ 2011-06-10 11:17 thilo
0 siblings, 0 replies; 9+ messages in thread
From: thilo @ 2011-06-10 11:17 UTC (permalink / raw)
To: linux-bluetooth
Hey,
>As Virtualbox does a direct usb passthrough to the client I could install the bluetooth adapter in windows with the original broadcom bluetooth driver.
>Once I opened the settings there and "saved" theses, the adapter finds bluetooth devices nicely under windows AND linux.
>
>Sadly I have no idea what the broadcom driver did to "activate" the adapter.
So, after a reboot the adapter is back in it's "no I don't want to do anything"-Mode and I have to activate it again via windows.
stop bluetooth daemon
unload btusb
boot windows VM with attached Bluetooth Device (boot til the login is visible, is enough)
dettach BD from Windows
load btusb
start bluetooth daemon
Now I can use the adapter as usual.
So there is definitley some initalization going on in the windows driver.
Any ideas how I can get more information whats going on during boot? Or is disassembling the windows driver the only way?
ciao
Thilo
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Support for 0489:e031 Foxconn / Hon Hai
@ 2011-06-27 14:57 thilo
2011-06-27 18:26 ` Peter Hurley
0 siblings, 1 reply; 9+ messages in thread
From: thilo @ 2011-06-27 14:57 UTC (permalink / raw)
To: linux-bluetooth
Hey again,
>>As Virtualbox does a direct usb passthrough to the client I could install the bluetooth adapter in windows with the original broadcom bluetooth driver.
>>Once I opened the settings there and "saved" theses, the adapter finds bluetooth devices nicely under windows AND linux.
>>
>>Sadly I have no idea what the broadcom driver did to "activate" the adapter.
>
>So, after a reboot the adapter is back in it's "no I don't want to do anything"-Mode and I have to activate it again via windows.
>
>stop bluetooth daemon
>unload btusb
>boot windows VM with attached Bluetooth Device (boot til the login is visible, is enough)
>dettach BD from Windows
>load btusb
>start bluetooth daemon
>
>Now I can use the adapter as usual.
>So there is definitley some initalization going on in the windows driver.
>
>Any ideas how I can get more information whats going on during boot? Or is disassembling the windows driver the only way?
>
I still have no idea how I might figure out what is done during the init of the windows driver. Since I need to unload the btusb module so windows can use the device, I have no chance to use hcidump.
Any ideas what I should try?
Ciao
Thilo
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Support for 0489:e031 Foxconn / Hon Hai
2011-06-27 14:57 Support for 0489:e031 Foxconn / Hon Hai thilo
@ 2011-06-27 18:26 ` Peter Hurley
0 siblings, 0 replies; 9+ messages in thread
From: Peter Hurley @ 2011-06-27 18:26 UTC (permalink / raw)
To: thilo@cestona.ro; +Cc: linux-bluetooth@vger.kernel.org
On Mon, 2011-06-27 at 10:57 -0400, thilo@cestona.ro wrote:
> Hey again,
>
> >>As Virtualbox does a direct usb passthrough to the client I could install the bluetooth adapter in windows with the original broadcom bluetooth driver.
> >>Once I opened the settings there and "saved" theses, the adapter finds bluetooth devices nicely under windows AND linux.
> >>
> >>Sadly I have no idea what the broadcom driver did to "activate" the adapter.
....
> I still have no idea how I might figure out what is done during the init of the windows driver. Since I need to unload the btusb module so windows can use the device, I have no chance to use hcidump.
> Any ideas what I should try?
There are several decent usb sniffers for windows - although I've never
tried them in a vm. This is a tough route to go though - even with a
complete device capture, separating what's relevant to your problem will
be *very* difficult.
Peter
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Support for 0489:e031 Foxconn / Hon Hai
@ 2011-08-09 20:23 Michael Markusch
0 siblings, 0 replies; 9+ messages in thread
From: Michael Markusch @ 2011-08-09 20:23 UTC (permalink / raw)
To: thilo; +Cc: linux-bluetooth
Hi Thilo,
I have the same problem with my new lifebook S761. Do you have already a
solution?
Many thanks,
Michael
> Hey,
>
> I got a new laptop and as usual new hardware has devices which aren't
> supported.
> In this case, it is the bluetooth adapter of the Fujitsu Lifebook
> E751.
>
> I have attached the lsusb -v output corresponding the adapter.
>
> Can someone please tell me, which information are also needed so
> support can be implemented?
>
> Should I contact Foxconn (or Broadcom) if they have a public spec?
>
> As it is a internal usb bluetooth adapter might it be enough to add
> the ID to btusb.c? (didn't work so far ;) )
>
> Any other hints?
>
> Ciao
> Thilo
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2011-08-09 20:23 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-27 14:57 Support for 0489:e031 Foxconn / Hon Hai thilo
2011-06-27 18:26 ` Peter Hurley
-- strict thread matches above, loose matches on Subject: below --
2011-08-09 20:23 Michael Markusch
2011-06-10 11:17 thilo
2011-06-08 13:33 thilo
2011-06-09 10:21 ` Marcel Holtmann
2011-06-01 11:48 thilo
2011-06-02 1:03 ` Marcel Holtmann
2011-06-02 7:23 ` Thilo Cestonaro
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).