* bcm43236 complient in the compat-wireless-3.6.81??? @ 2013-12-19 10:03 Naughtboy 2013-12-19 12:27 ` Hauke Mehrtens 0 siblings, 1 reply; 11+ messages in thread From: Naughtboy @ 2013-12-19 10:03 UTC (permalink / raw) To: linux-wireless hi erveryone ! i have a usb dongle bcm43236 i wan to trsan it in the mips bcm47xx but i search in hte www , and didn't find the driver for bcm43236 linux soucre code !! i have find and study http://wireless.kernel.org/en/users/Drivers/b43 and find http://wireless.kernel.org/en/users/Drivers/b43 do nothing usefull !! anyone can do one hand? thanks advance !! -----Naughyboy ! ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: bcm43236 complient in the compat-wireless-3.6.81??? 2013-12-19 10:03 bcm43236 complient in the compat-wireless-3.6.81??? Naughtboy @ 2013-12-19 12:27 ` Hauke Mehrtens [not found] ` <CAKH5=LsaEw7GEHs5nb1omDeSMmcoFSXo8EEy+DeXvyXF5_1M_g@mail.gmail.com> 0 siblings, 1 reply; 11+ messages in thread From: Hauke Mehrtens @ 2013-12-19 12:27 UTC (permalink / raw) To: Naughtboy, linux-wireless On 12/19/2013 11:03 AM, Naughtboy wrote: > hi erveryone ! > i have a usb dongle bcm43236 > i wan to trsan it in the mips bcm47xx > but i search in hte www , and didn't find the driver for bcm43236 > linux soucre code !! > i have find and study http://wireless.kernel.org/en/users/Drivers/b43 > > and find http://wireless.kernel.org/en/users/Drivers/b43 do nothing > usefull !! > > anyone can do one hand? > thanks advance !! > > -----Naughyboy ! Hi, I assume you have a bcm43236 rev 2 as all the bcm43236s connected to a MIPS BCM47XX SoC I saw have that rev. There is probably no open source driver for the bcm43236 rev 2, just rev 3 is supported by brcmfmac. Hauke ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAKH5=LsaEw7GEHs5nb1omDeSMmcoFSXo8EEy+DeXvyXF5_1M_g@mail.gmail.com>]
* Re: bcm43236 complient in the compat-wireless-3.6.81??? [not found] ` <CAKH5=LsaEw7GEHs5nb1omDeSMmcoFSXo8EEy+DeXvyXF5_1M_g@mail.gmail.com> @ 2013-12-19 14:21 ` Hauke Mehrtens 2013-12-19 15:41 ` Arend van Spriel 0 siblings, 1 reply; 11+ messages in thread From: Hauke Mehrtens @ 2013-12-19 14:21 UTC (permalink / raw) To: Naughtboy; +Cc: linux-wireless@vger.kernel.org On 12/19/2013 03:14 PM, Naughtboy wrote: > hello guys > rev 3 ? where can i gain this linux source code ? > thanks advnace This device is supported by brcmfmac: http://wireless.kernel.org/en/users/Drivers/brcm80211 The source code is in a recent linux kernel or in backports: http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/ Hauke > > 2013/12/19 Hauke Mehrtens <hauke@hauke-m.de>: >> On 12/19/2013 11:03 AM, Naughtboy wrote: >>> hi erveryone ! >>> i have a usb dongle bcm43236 >>> i wan to trsan it in the mips bcm47xx >>> but i search in hte www , and didn't find the driver for bcm43236 >>> linux soucre code !! >>> i have find and study http://wireless.kernel.org/en/users/Drivers/b43 >>> >>> and find http://wireless.kernel.org/en/users/Drivers/b43 do nothing >>> usefull !! >>> >>> anyone can do one hand? >>> thanks advance !! >>> >>> -----Naughyboy ! >> >> Hi, >> >> I assume you have a bcm43236 rev 2 as all the bcm43236s connected to a >> MIPS BCM47XX SoC I saw have that rev. There is probably no open source >> driver for the bcm43236 rev 2, just rev 3 is supported by brcmfmac. >> >> Hauke ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: bcm43236 complient in the compat-wireless-3.6.81??? 2013-12-19 14:21 ` Hauke Mehrtens @ 2013-12-19 15:41 ` Arend van Spriel 2013-12-20 7:57 ` Rafał Miłecki [not found] ` <CAKH5=LvUqfyqW5NQGNzCec2yVrzFqFWCbtQvF5ZL=cjkh=9HOw@mail.gmail.com> 0 siblings, 2 replies; 11+ messages in thread From: Arend van Spriel @ 2013-12-19 15:41 UTC (permalink / raw) To: Hauke Mehrtens, Naughtboy; +Cc: linux-wireless@vger.kernel.org On 12/19/2013 03:21 PM, Hauke Mehrtens wrote: > On 12/19/2013 03:14 PM, Naughtboy wrote: >> hello guys >> rev 3 ? where can i gain this linux source code ? >> thanks advnace > > This device is supported by brcmfmac: > http://wireless.kernel.org/en/users/Drivers/brcm80211 It is in the kernel tree under 'drivers/net/wireless/brcm80211/brcmfmac'. We only support rev 3 because rev 2 and earlier do not have enough memory to run fullmac firmware. However, I have not found any rev 3 on the market. If you have please let me know. Gr. AvS > The source code is in a recent linux kernel or in backports: > http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/ > > Hauke > >> >> 2013/12/19 Hauke Mehrtens <hauke@hauke-m.de>: >>> On 12/19/2013 11:03 AM, Naughtboy wrote: >>>> hi erveryone ! >>>> i have a usb dongle bcm43236 >>>> i wan to trsan it in the mips bcm47xx >>>> but i search in hte www , and didn't find the driver for bcm43236 >>>> linux soucre code !! >>>> i have find and study http://wireless.kernel.org/en/users/Drivers/b43 >>>> >>>> and find http://wireless.kernel.org/en/users/Drivers/b43 do nothing >>>> usefull !! >>>> >>>> anyone can do one hand? >>>> thanks advance !! >>>> >>>> -----Naughyboy ! >>> >>> Hi, >>> >>> I assume you have a bcm43236 rev 2 as all the bcm43236s connected to a >>> MIPS BCM47XX SoC I saw have that rev. There is probably no open source >>> driver for the bcm43236 rev 2, just rev 3 is supported by brcmfmac. >>> >>> Hauke > > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: bcm43236 complient in the compat-wireless-3.6.81??? 2013-12-19 15:41 ` Arend van Spriel @ 2013-12-20 7:57 ` Rafał Miłecki 2013-12-20 12:24 ` Arend van Spriel [not found] ` <CAKH5=LvUqfyqW5NQGNzCec2yVrzFqFWCbtQvF5ZL=cjkh=9HOw@mail.gmail.com> 1 sibling, 1 reply; 11+ messages in thread From: Rafał Miłecki @ 2013-12-20 7:57 UTC (permalink / raw) To: Arend van Spriel Cc: Hauke Mehrtens, Naughtboy, linux-wireless@vger.kernel.org 2013/12/19 Arend van Spriel <arend@broadcom.com>: > It is in the kernel tree under > 'drivers/net/wireless/brcm80211/brcmfmac'. We only support rev 3 because > rev 2 and earlier do not have enough memory to run fullmac firmware. > However, I have not found any rev 3 on the market. If you have please > let me know. Could you say something more about rev 2? How does it work with internal Broadcom driver? Is the firmware stored somewhere else? Does it have some another kind of memory? Apart from the firmware storing issue, is the communication between driver and hardware the same? ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: bcm43236 complient in the compat-wireless-3.6.81??? 2013-12-20 7:57 ` Rafał Miłecki @ 2013-12-20 12:24 ` Arend van Spriel 2014-01-12 14:17 ` Rafał Miłecki 0 siblings, 1 reply; 11+ messages in thread From: Arend van Spriel @ 2013-12-20 12:24 UTC (permalink / raw) To: Rafał Miłecki Cc: Hauke Mehrtens, Naughtboy, linux-wireless@vger.kernel.org On 12/20/2013 08:57 AM, Rafał Miłecki wrote: > 2013/12/19 Arend van Spriel <arend@broadcom.com>: >> It is in the kernel tree under >> 'drivers/net/wireless/brcm80211/brcmfmac'. We only support rev 3 because >> rev 2 and earlier do not have enough memory to run fullmac firmware. >> However, I have not found any rev 3 on the market. If you have please >> let me know. > > Could you say something more about rev 2? How does it work with > internal Broadcom driver? Is the firmware stored somewhere else? Does > it have some another kind of memory? It has a split-mac design. So at one end the spectrum there is mac80211-type drivers and at the other side are fullmac drivers like brcmfmac. rev 2 driver sits right in the middle of that with part of the 802.11 stack running on the host and part on the device. This device has not enough memory to run the fullmac firmware. Gr. AvS > Apart from the firmware storing issue, is the communication between > driver and hardware the same? > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: bcm43236 complient in the compat-wireless-3.6.81??? 2013-12-20 12:24 ` Arend van Spriel @ 2014-01-12 14:17 ` Rafał Miłecki 2014-01-12 14:33 ` Arend van Spriel 0 siblings, 1 reply; 11+ messages in thread From: Rafał Miłecki @ 2014-01-12 14:17 UTC (permalink / raw) To: Arend van Spriel Cc: Hauke Mehrtens, Naughtboy, linux-wireless@vger.kernel.org [-- Attachment #1: Type: text/plain, Size: 1711 bytes --] 2013/12/20 Arend van Spriel <arend@broadcom.com>: > On 12/20/2013 08:57 AM, Rafał Miłecki wrote: >> 2013/12/19 Arend van Spriel <arend@broadcom.com>: >>> It is in the kernel tree under >>> 'drivers/net/wireless/brcm80211/brcmfmac'. We only support rev 3 because >>> rev 2 and earlier do not have enough memory to run fullmac firmware. >>> However, I have not found any rev 3 on the market. If you have please >>> let me know. >> >> Could you say something more about rev 2? How does it work with >> internal Broadcom driver? Is the firmware stored somewhere else? Does >> it have some another kind of memory? > > It has a split-mac design. So at one end the spectrum there is > mac80211-type drivers and at the other side are fullmac drivers like > brcmfmac. rev 2 driver sits right in the middle of that with part of the > 802.11 stack running on the host and part on the device. This device has > not enough memory to run the fullmac firmware. Thanks for your explanation. I think I understand now what means WLC_HIGH, WLC_LOW, WLC_SPLIT you can see in 0001-Staging-Add-initial-release-of-brcm80211-Broadcom-80.patch. I guess that softmac devices need WLC_HIGH and WLC_LOW, split devices (like BCM43231) need WLC_HIGH (because LOW is implemented in firmware) and full MAC devices need none of above. As questions about these chipset come over and over, I added a new section to the brcm80211 wiki page: http://wireless.kernel.org/en/users/Drivers/brcm80211#Unsupported_Chips I hope it's OK for you. Btw. if anyone is interested, I've written a minimal user-space app to read device info (DL_GETVER) from Broadcom USB dongle. gcc -lusb-1.0 main.c -o bcmid -- Rafał [-- Attachment #2: main.c --] [-- Type: text/x-csrc, Size: 1968 bytes --] #include <stdio.h> #include <endian.h> #include <libusb-1.0/libusb.h> #define BCM_VENDOR_ID 0x0846 #define BCM_DEVICE_ID 0x9011 #define DL_GETVER 5 struct bcmusb_id { uint32_t chip; uint32_t chiprev; /* Below are returned by recent cards only */ uint32_t ramsize; uint32_t remapbase; uint32_t boardtype; uint32_t boardrev; }; int main() { libusb_context *context = NULL; libusb_device_handle *handle; struct bcmusb_id id; int bytes, err; libusb_init(&context); handle = libusb_open_device_with_vid_pid(context, BCM_VENDOR_ID, BCM_DEVICE_ID); if (!handle) { printf("Couldn't find/open %04X:%04X device (is it available? are you root?)\n", BCM_VENDOR_ID, BCM_DEVICE_ID); return -1; } err = libusb_claim_interface(handle, 0); if (err) { printf("Couldn't claim %04X:%04X device interface (another driver using it?)\n", BCM_VENDOR_ID, BCM_DEVICE_ID); return -2; } bytes = libusb_control_transfer(handle, LIBUSB_ENDPOINT_IN | LIBUSB_REQUEST_TYPE_VENDOR | LIBUSB_RECIPIENT_INTERFACE, DL_GETVER, 0, /* wValue */ 0, /* wIndex */ (unsigned char *)&id, sizeof(struct bcmusb_id), 500); if (bytes < 0) { printf("libusb_control_transfer error: %d\n", bytes); return bytes; } if (bytes == 8 || bytes == 24) { printf("[id] chip: %04X\n", le32toh(id.chip)); printf("[id] chiprev: %04X\n", le32toh(id.chiprev)); if (bytes == 24) { printf("[id] ramsize: %04X\n", le32toh(id.ramsize)); printf("[id] remapbase: %04X\n", le32toh(id.remapbase)); printf("[id] boardtype: %04X\n", le32toh(id.boardtype)); printf("[id] boardrev: %04X\n", le32toh(id.boardrev)); } } else { printf("libusb_control_transfer returned unexpected amount of bytes (%d)\n", bytes); return -3; } err = libusb_release_interface(handle, 0); if (err) { printf("Couldn't release %04X:%04X device interface\n", BCM_VENDOR_ID, BCM_DEVICE_ID); return -4; } libusb_close(handle); libusb_exit(context); } ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: bcm43236 complient in the compat-wireless-3.6.81??? 2014-01-12 14:17 ` Rafał Miłecki @ 2014-01-12 14:33 ` Arend van Spriel 2014-01-12 20:13 ` Rafał Miłecki 0 siblings, 1 reply; 11+ messages in thread From: Arend van Spriel @ 2014-01-12 14:33 UTC (permalink / raw) To: Rafał Miłecki Cc: Hauke Mehrtens, Naughtboy, linux-wireless@vger.kernel.org On 01/12/2014 03:17 PM, Rafał Miłecki wrote: > 2013/12/20 Arend van Spriel <arend@broadcom.com>: >> On 12/20/2013 08:57 AM, Rafał Miłecki wrote: >>> 2013/12/19 Arend van Spriel <arend@broadcom.com>: >>>> It is in the kernel tree under >>>> 'drivers/net/wireless/brcm80211/brcmfmac'. We only support rev 3 because >>>> rev 2 and earlier do not have enough memory to run fullmac firmware. >>>> However, I have not found any rev 3 on the market. If you have please >>>> let me know. >>> >>> Could you say something more about rev 2? How does it work with >>> internal Broadcom driver? Is the firmware stored somewhere else? Does >>> it have some another kind of memory? >> >> It has a split-mac design. So at one end the spectrum there is >> mac80211-type drivers and at the other side are fullmac drivers like >> brcmfmac. rev 2 driver sits right in the middle of that with part of the >> 802.11 stack running on the host and part on the device. This device has >> not enough memory to run the fullmac firmware. > > Thanks for your explanation. I think I understand now what means > WLC_HIGH, WLC_LOW, WLC_SPLIT you can see in > 0001-Staging-Add-initial-release-of-brcm80211-Broadcom-80.patch. I > guess that softmac devices need WLC_HIGH and WLC_LOW, split devices > (like BCM43231) need WLC_HIGH (because LOW is implemented in firmware) > and full MAC devices need none of above. Yeah. The brcmfmac driver for fullmac devices is a separate driver design based on bcmdhd. > As questions about these chipset come over and over, I added a new > section to the brcm80211 wiki page: > http://wireless.kernel.org/en/users/Drivers/brcm80211#Unsupported_Chips > I hope it's OK for you. Fine and thanks. Let's see how often another such question pops up. > Btw. if anyone is interested, I've written a minimal user-space app to > read device info (DL_GETVER) from Broadcom USB dongle. > gcc -lusb-1.0 main.c -o bcmid I see fixed definition for vendor and device id. Given that they differ from what we have in brcmfmac it may be good to use command line argument(s) for these. Regards, Arend ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: bcm43236 complient in the compat-wireless-3.6.81??? 2014-01-12 14:33 ` Arend van Spriel @ 2014-01-12 20:13 ` Rafał Miłecki 2014-01-13 16:18 ` Arend van Spriel 0 siblings, 1 reply; 11+ messages in thread From: Rafał Miłecki @ 2014-01-12 20:13 UTC (permalink / raw) To: Arend van Spriel Cc: Hauke Mehrtens, Naughtboy, linux-wireless@vger.kernel.org 2014/1/12 Arend van Spriel <arend@broadcom.com>: >> Btw. if anyone is interested, I've written a minimal user-space app to >> read device info (DL_GETVER) from Broadcom USB dongle. >> gcc -lusb-1.0 main.c -o bcmid > > I see fixed definition for vendor and device id. Given that they differ > from what we have in brcmfmac it may be good to use command line > argument(s) for these. I don't see any real usage possibilities for this app, I just wanted to see how "libusb" works and see what's really inside of my WNA3100. I don't think anyone is really going to use it ;) Just shared it since I already got it ;) -- Rafał ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: bcm43236 complient in the compat-wireless-3.6.81??? 2014-01-12 20:13 ` Rafał Miłecki @ 2014-01-13 16:18 ` Arend van Spriel 0 siblings, 0 replies; 11+ messages in thread From: Arend van Spriel @ 2014-01-13 16:18 UTC (permalink / raw) To: Rafał Miłecki Cc: Hauke Mehrtens, Naughtboy, linux-wireless@vger.kernel.org On 01/12/2014 09:13 PM, Rafał Miłecki wrote: > 2014/1/12 Arend van Spriel <arend@broadcom.com>: >>> Btw. if anyone is interested, I've written a minimal user-space app to >>> read device info (DL_GETVER) from Broadcom USB dongle. >>> gcc -lusb-1.0 main.c -o bcmid >> >> I see fixed definition for vendor and device id. Given that they differ >> from what we have in brcmfmac it may be good to use command line >> argument(s) for these. > > I don't see any real usage possibilities for this app, I just wanted > to see how "libusb" works and see what's really inside of my WNA3100. > I don't think anyone is really going to use it ;) Just shared it since > I already got it ;) > Well, we could put it on the wiki page so people can check before asking the question. Gr. AvS ^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <CAKH5=LvUqfyqW5NQGNzCec2yVrzFqFWCbtQvF5ZL=cjkh=9HOw@mail.gmail.com>]
* Re: bcm43236 complient in the compat-wireless-3.6.81??? [not found] ` <CAKH5=LvUqfyqW5NQGNzCec2yVrzFqFWCbtQvF5ZL=cjkh=9HOw@mail.gmail.com> @ 2013-12-20 9:30 ` Arend van Spriel 0 siblings, 0 replies; 11+ messages in thread From: Arend van Spriel @ 2013-12-20 9:30 UTC (permalink / raw) To: Naughtboy, Hauke Mehrtens; +Cc: linux-wireless On 12/20/2013 10:20 AM, Naughtboy wrote: > hi guys > > just you kown ,the bcm43236 is the new chip to support dual band 2.4G and > 5.8G > rev3?(what is meaning) it means is the third product ? or it means > linux-3.xx? (just you said it most likely the first meanig ) > http://wireless.kernel.org/en/users/Drivers/brcm80211 > and i try transplant it into linux-2.6.22 and occur lots of interface of > mistakes , it just suport linux-3.xx (and it transplant into linux-2.6.22 > it nedd modfiy lots interface ) > > and the drivers/net/wireless/brcm80211/brcmfmac just support (and did't > suport rev2 ==linux-2.6) > just you request , bcm43236 has a product in the market ,yu can see the > follow ! > (however , my problems , > http://wireless.kernel.org/en/users/Drivers/brcm80211 > drivers/net/wireless/brcm80211/brcmfmac > it enough make bcm43236 working????) > > bcm43236 has a product in the market: > http://to-link.net/ProductShow.asp?ID=116 Your "english" is difficult to follow. Anyway, we are talking about chip revisions. It has nothing to do with linux kernel versions. However, if you want to use it on an ancient 2.6.22 kernel you better use the backports that Hauke referred to. Unfortunately for BRCMFMAC it only goes back to 2.6.29. Maybe in general backports only goes back till 2.6.24 (not sure). If you get the driver working it will spill out in the kernel log whether your bcm43236 has a good *chip* revision, ie. chiprev >= 3. Regards, Arend > 2013/12/19 Arend van Spriel <arend@broadcom.com> > >> On 12/19/2013 03:21 PM, Hauke Mehrtens wrote: >>> On 12/19/2013 03:14 PM, Naughtboy wrote: >>>> hello guys >>>> rev 3 ? where can i gain this linux source code ? >>>> thanks advnace >>> >>> This device is supported by brcmfmac: >>> http://wireless.kernel.org/en/users/Drivers/brcm80211 >> >> It is in the kernel tree under >> 'drivers/net/wireless/brcm80211/brcmfmac'. We only support rev 3 because >> rev 2 and earlier do not have enough memory to run fullmac firmware. >> However, I have not found any rev 3 on the market. If you have please >> let me know. >> >> Gr. AvS >> >>> The source code is in a recent linux kernel or in backports: >>> http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/ >>> >>> Hauke >>> >>>> >>>> 2013/12/19 Hauke Mehrtens <hauke@hauke-m.de>: >>>>> On 12/19/2013 11:03 AM, Naughtboy wrote: >>>>>> hi erveryone ! >>>>>> i have a usb dongle bcm43236 >>>>>> i wan to trsan it in the mips bcm47xx >>>>>> but i search in hte www , and didn't find the driver for bcm43236 >>>>>> linux soucre code !! >>>>>> i have find and study >> http://wireless.kernel.org/en/users/Drivers/b43 >>>>>> >>>>>> and find http://wireless.kernel.org/en/users/Drivers/b43 do >> nothing >>>>>> usefull !! >>>>>> >>>>>> anyone can do one hand? >>>>>> thanks advance !! >>>>>> >>>>>> -----Naughyboy ! >>>>> >>>>> Hi, >>>>> >>>>> I assume you have a bcm43236 rev 2 as all the bcm43236s connected to a >>>>> MIPS BCM47XX SoC I saw have that rev. There is probably no open source >>>>> driver for the bcm43236 rev 2, just rev 3 is supported by brcmfmac. >>>>> >>>>> Hauke >>> >>> -- >>> To unsubscribe from this list: send the line "unsubscribe >> linux-wireless" in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >> >> > ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2014-01-13 16:18 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-19 10:03 bcm43236 complient in the compat-wireless-3.6.81??? Naughtboy
2013-12-19 12:27 ` Hauke Mehrtens
[not found] ` <CAKH5=LsaEw7GEHs5nb1omDeSMmcoFSXo8EEy+DeXvyXF5_1M_g@mail.gmail.com>
2013-12-19 14:21 ` Hauke Mehrtens
2013-12-19 15:41 ` Arend van Spriel
2013-12-20 7:57 ` Rafał Miłecki
2013-12-20 12:24 ` Arend van Spriel
2014-01-12 14:17 ` Rafał Miłecki
2014-01-12 14:33 ` Arend van Spriel
2014-01-12 20:13 ` Rafał Miłecki
2014-01-13 16:18 ` Arend van Spriel
[not found] ` <CAKH5=LvUqfyqW5NQGNzCec2yVrzFqFWCbtQvF5ZL=cjkh=9HOw@mail.gmail.com>
2013-12-20 9:30 ` Arend van Spriel
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).