Re: GsmBluetooth state file for gta02
Federico Out of interest, wouldn't it be possible to route the GSM audio through the CPU, and then through BT? It may be less then optimal, but I don't see why it wouldn't work? yes... it should be possible to reset the bluetooth adapter to use cpu (hci) routing. I haven't tried this (and it gets a little scary for bricking, etc) but the command to temporarily make the change and reset the adaper looks like: bccmd psset -r 0x1ab 0 this may only take after running it twice. a better option for testing out hci routing would be to turn off the internal bluetooth adapter and attach a csr-based usb adapter to the miniusb port. If you've got a good adapter, after plugging it in you should be able to run: hciconfig hci0 revision and see SCO mapping: HCI then you can follow the instructions that apply to using voice bluetooth audio on a desktop machine. getting the gsm call to route over it will be another hurdle--it's why I asked in another thread if it's possible to record gsm calls. the kernel support for doing hci-routed audio is vastly better in the latest kernel using the btusb driver. That driver may still be in flux. -- Brad ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Jim Morris escreveu: Cesar Eduardo Barros wrote So, you just need to find out: - How to switch bluetooth audio I/O to these PCM pins (should be something in the HCI-USB standard). I think bluez driver already does that. I made it work on my PC for instance. Your PC probably doesn't use that mode. It probably sends the audio via the USB interface (which, if you use a USB BT dongle, is the only way available). -- Cesar Eduardo Barros [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
most chips default to the right sco routing... there were a few misconfigured usb adapters out there but this has been less of a problem recently. The neo's chip is routed to pcm. You can verify this by running hciconfig hci0 revision On Tue, Sep 2, 2008 at 8:12 PM, Cesar Eduardo Barros [EMAIL PROTECTED] wrote: Jim Morris escreveu: Cesar Eduardo Barros wrote So, you just need to find out: - How to switch bluetooth audio I/O to these PCM pins (should be something in the HCI-USB standard). I think bluez driver already does that. I made it work on my PC for instance. Your PC probably doesn't use that mode. It probably sends the audio via the USB interface (which, if you use a USB BT dongle, is the only way available). -- Cesar Eduardo Barros [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Brad ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
On Wed, Sep 3, 2008 at 4:12 AM, Cesar Eduardo Barros [EMAIL PROTECTED] wrote: Jim Morris escreveu: Cesar Eduardo Barros wrote So, you just need to find out: - How to switch bluetooth audio I/O to these PCM pins (should be something in the HCI-USB standard). I think bluez driver already does that. I made it work on my PC for instance. Your PC probably doesn't use that mode. It probably sends the audio via the USB interface (which, if you use a USB BT dongle, is the only way available). Out of interest, wouldn't it be possible to route the GSM audio through the CPU, and then through BT? It may be less then optimal, but I don't see why it wouldn't work? Cheers, Federico ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Cesar Eduardo Barros wrote That's because the Bluetooth is in another chip. For that, you need the full schematics: http://downloads.openmoko.org/schematics/GTA02/Schematics_Freerunner-GTA02_A5-A7cumulative_public_RC0.pdf I looked at the schematics, and the BT chip is directly connected to the audio chip. The BT chip setup is done by bluez, and it appears pcm in/out is always on and no additional setup required (other than pairing and setting up the headset). The very first diagram (page 2) shows how the chips fit together. There you can see how the bluetooth chip is connected to the codec: the PCM pins. There seems to be a comment saying something about BT Codec DAI on neo1973_gta02_wm8753.c, which seems related. If it is it is totally beyond me to see where and how this would be setup So, you just need to find out: - How to switch bluetooth audio I/O to these PCM pins (should be something in the HCI-USB standard). I think bluez driver already does that. I made it work on my PC for instance. - How to route within the codec between the PCM pins and the pins which are connected to the GSM chip (these pins are also shown in the diagram). That also seems to be set in the .state files which are GTA01 specific, I created some GTA02 ones but no hint of audio thru BT. (I probably missed something like the Neo Mode setting, but wait.. they took that out and did not document what it was replaced with!) I officially give up on this, as I simply cannot make any further progress, I have uploaded the gta02 compatible state files to the wiki, and I hope someone with more patience than me can guess the rest, because guessing is about all that is left. I am totally frustrated by this, and the total lack of interest by anyone at OM to get this working. I am very close to sending the FR back under false advertising laws, as no working BT headset makes it useless as a GSM phone in the state I live in, and it is advertised as having BT headset capability and I have spent a lot of time filling in for OM to try to get this to work. If OM can give me at least a time frame when they can look into this I'd appreciate it, because I am starting to think that BT headset will not work in GTA02, like it didn't work in GTA01, and OM is avoiding having to admit that publicly. All other conspiracy theories are welcome ;) A VERY frustrated user! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
I notice there is a bug filed against this issue... http://docs.openmoko.org/trac/ticket/113 It was filed 20 months ago! I guess that says what the priority of this is. If anyone else is as pissed as I am about the lack of BT support, please hassle OM management to get this priority raised. Thanks Jim ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Jim Morris wrote: I notice there is a bug filed against this issue... http://docs.openmoko.org/trac/ticket/113 It was filed 20 months ago! I guess that says what the priority of this is. If anyone else is as pissed as I am about the lack of BT support, please hassle OM management to get this priority raised. Am I wrong or someone got it working in qtopia? If it is true, maybe you could get some infos from their sources... -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Marco Trevisan (Treviño) wrote: Jim Morris wrote: I notice there is a bug filed against this issue... http://docs.openmoko.org/trac/ticket/113 It was filed 20 months ago! I guess that says what the priority of this is. If anyone else is as pissed as I am about the lack of BT support, please hassle OM management to get this priority raised. Am I wrong or someone got it working in qtopia? If it is true, maybe you could get some infos from their sources... Qtopia allows you to pair from the GUI, I got that working, however once paired the audio does nothing as Qtopia does not load the alsa state. Basically the situation is the same across all dists, and the solution will be the same for all dists AFAIK. We need a working alsa.state file (I think I may have one, or at least one that is pretty close), and we need to understand how alsa and bluez work together to make the PCM from the bluetooth chip interact with the wolfson audio chip. and whatever else used to be done if you set the Neo Mode in alsa to bluetooth. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Jim Morris wrote: Cesar Eduardo Barros wrote: Jim Morris escreveu: One thing that may help, is if someone could provide a mapping of the wolfson registers as documented in the WM8753L pdf to the alsa controls. Someone had to have written the code that twiddles the registers in that chip, and would know which also control matches which register. That would be sound/soc/codecs/wm8753.c and sound/soc/s3c24xx/neo1973_gta02_wm8753.c on the kernel source code. Take a look: http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/codecs/wm8753.c;hb=stable http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/s3c24xx/neo1973_gta02_wm8753.c;hb=stable The mapping is there, you only have to find out how it's described. Thanks for the pointers. Thats 2,000 lines of code that is about as clear as mud! (and I've written audio drivers before). There is no mention of Bluetooth in these drivers, and no indication how to switch into bluetooth mode. Obviously gta01 was very different, and it is not even clear that the gsmbluetooth.state even worked on a gta01, at least I've never seen any gta01 user claim they had it working. bluetooth audio on the gta01 will never work, even with that bluetooth alsa state. -- Lorn 'ljp' Potter Software Engineer, Systems Group, Trolltech, a Nokia company ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Jim, Just wanted to say that your efforts on making bluetooth headsets usable is highly appreciated! A question: I guess you're trying to route the GSM audio to bluetooth, is this right or are you looking at routing generic audio (from mplayer) to bluetooth? Will you also be able to choose between SCO A2DP then in anyway? (obviously A2DP won't make it for GSM phone calls - unless you're the silent type) Thanks again, Fredrik signature.asc Description: Detta är en digitalt signerad meddelandedel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Fredrik Wendt wrote: Jim, Just wanted to say that your efforts on making bluetooth headsets usable is highly appreciated! A question: I guess you're trying to route the GSM audio to bluetooth, is this right or are you looking at routing generic audio (from mplayer) to bluetooth? Will you also be able to choose between SCO A2DP then in anyway? (obviously A2DP won't make it for GSM phone calls - unless you're the silent type) I'm just trying to get the BT to GSM path and GSM to BT path in the chip to work. A2DP for stereo (CPU to BT) is a different path, and apparently people have been able to get that to work, although with mixed results. Check the Wiki for a recipe to make that work. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Lorn Potter wrote: bluetooth audio on the gta01 will never work, even with that bluetooth alsa state. Ok so where did that gsmbluetooth.state come from and why did someone do it if it never worked? Unfortunately I was only partially able to generate a gta02 version of the state file, as many of the controls have no equivalent in gta02. I guess I should try what I have it may work. I'll report back. Then the question for you is if it does work, how do we get Qtopia to load the state file automatically on a gsm call when BT is enabled? -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Lorn Potter wrote:
Jim Morris wrote:
Cesar Eduardo Barros wrote:
Jim Morris escreveu:
One thing that may help, is if someone could provide a mapping of
the wolfson registers as documented in the WM8753L pdf to the alsa
controls. Someone had to have written the code that twiddles the
registers in that chip, and would know which also control matches
which register.
That would be sound/soc/codecs/wm8753.c and
sound/soc/s3c24xx/neo1973_gta02_wm8753.c on the kernel source code.
Take a look:
http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/codecs/wm8753.c;hb=stable
http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/s3c24xx/neo1973_gta02_wm8753.c;hb=stable
The mapping is there, you only have to find out how it's described.
Thanks for the pointers. Thats 2,000 lines of code that is about as
clear as mud! (and I've written audio drivers before).
There is no mention of Bluetooth in these drivers, and no indication
how to switch into bluetooth mode.
Obviously gta01 was very different, and it is not even clear that the
gsmbluetooth.state even worked on a gta01, at least I've never seen
any gta01 user claim they had it working.
bluetooth audio on the gta01 will never work, even with that bluetooth
alsa state.
Ok well it didn't work, attached is the gsmbluetooth.state file I am trying to use if anyone is
interested and wants to try it. I set this as best I could from comparing the differences between
the gsmhandset.state and gsmheadset.state for the gta01 and transcribing to gta02 as best as
possible given the undocumented differences between the two.
After calling the cell phone I did an alsactl -f gsmbluetooth.state restore.
In the process I just discovered the Qtopia (this is for you Lorn ;) did not load
/usr/share/openmoko/scenarios/gsmhandset.state when the call was answered, I had to do it manually,
I'm pretty sure this is a regression.
Also the options available in the menu when in a call to set speakerphone handset or bluetooth do
not seem to do anything.
I'm pretty much out of ideas on how to get a working gsmbluetooth.state file for gta02, so someone
else chime in if you think of anything.
I see this as a show stopper for the unit being usable as a phone so if anyone at OM cares I'd get
on it ASAP.
--
Jim Morris, http://blog.wolfman.com
state.neo1973gta02 {
control.1 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'PCM Volume'
value.0 0
value.1 0
}
control.2 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'ADC Capture Volume'
value.0 0
value.1 0
}
control.3 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Headphone Playback Volume'
value.0 96
value.1 96
}
control.4 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Speaker Playback Volume'
value.0 0
value.1 0
}
control.5 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 127'
iface MIXER
name 'Mono Playback Volume'
value 103
}
control.6 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 7'
iface MIXER
name 'Bypass Playback Volume'
value.0 7
value.1 7
}
control.7 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 7'
iface MIXER
name 'Sidetone Playback Volume'
value.0 0
value.1 0
}
control.8 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 7'
iface MIXER
name 'Voice Playback Volume'
value.0 0
value.1 0
}
control.9 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Headphone Playback ZC
Re: GsmBluetooth state file for gta02
Jim Morris escreveu: Cesar Eduardo Barros wrote: Jim Morris escreveu: One thing that may help, is if someone could provide a mapping of the wolfson registers as documented in the WM8753L pdf to the alsa controls. Someone had to have written the code that twiddles the registers in that chip, and would know which also control matches which register. That would be sound/soc/codecs/wm8753.c and sound/soc/s3c24xx/neo1973_gta02_wm8753.c on the kernel source code. Take a look: http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/codecs/wm8753.c;hb=stable http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/s3c24xx/neo1973_gta02_wm8753.c;hb=stable The mapping is there, you only have to find out how it's described. Thanks for the pointers. Thats 2,000 lines of code that is about as clear as mud! (and I've written audio drivers before). There is no mention of Bluetooth in these drivers, and no indication how to switch into bluetooth mode. That's because the Bluetooth is in another chip. For that, you need the full schematics: http://downloads.openmoko.org/schematics/GTA02/Schematics_Freerunner-GTA02_A5-A7cumulative_public_RC0.pdf The very first diagram (page 2) shows how the chips fit together. There you can see how the bluetooth chip is connected to the codec: the PCM pins. There seems to be a comment saying something about BT Codec DAI on neo1973_gta02_wm8753.c, which seems related. So, you just need to find out: - How to switch bluetooth audio I/O to these PCM pins (should be something in the HCI-USB standard). - How to route within the codec between the PCM pins and the pins which are connected to the GSM chip (these pins are also shown in the diagram). A possible hint: back when trying to find out why the GTA01 used too much power when off, we had to find how to turn off the audio amp (another chip). I saw a concept called a scenario, which is some sort of predefined audio routing on the kernel. So perhaps you just have to find the correct scenario and how to select it. On neo1973_wm8753.c, it's the Neo Mode control; for some very strange reason, there's no equivalent on neo1973_gta02_wm8753.c, however the defines are still there in the top of the file! I really don't see how we are supposed to figure this stuff out, without any help from Openmoko. With the schematics. That's one of the reasons they were released. With them, the detailed datasheet for the chips, and the kernel source code, you can do a lot. -- Cesar Eduardo Barros [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
GsmBluetooth state file for gta02
I am still trying to get a bluetooth headset to work with the GTA02. I found on the Wiki a pointer to this state file http://opensource.wolfsonmicro.com/~gg/neo1973/gsmbluetooth.state however it is gta01 specific, and around control 51, all the control numbers change as gta02 seems to have an additional control there. So I am slowly going through all the controls from 51 onwards and trying to see what changed between gta01 and gta02. Hopefully at the end I will have a gsmbluetooth.state file that will work with gta02. If someone else has already done this please let me know, as this will be pretty tedious. Thanks Jim -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Jim Morris wrote:
I am still trying to get a bluetooth headset to work with the GTA02.
I found on the Wiki a pointer to this state file
http://opensource.wolfsonmicro.com/~gg/neo1973/gsmbluetooth.state
however it is gta01 specific, and around control 51, all the control numbers
change as gta02 seems
to have an additional control there.
So I am slowly going through all the controls from 51 onwards and trying to
see what changed between
gta01 and gta02.
By going through line by line I see the differences that the old gta01 state
files had between bt
and headset states, so fixing them up in a newer gta02 state file was ok until
gta01 control 87
upwards. None of these controls appear in a gta02 state file, so there seems to
be no equivalent
settings. Especially control 90, which seems pretty important for bluetooth but
has no equivalent in
the gt02 state file.
So can someone please explain what is going on here? Thanks
Here are the gta01 controls that do not fit into gta02 state files...
control.87 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 31'
iface MIXER
name 'Amp Right Playback Volume'
value 0
}
control.88 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 31'
iface MIXER
name 'Amp Mono Playback Volume'
value 0
}
control.89 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 Off
comment.item.1 'Call Speaker'
comment.item.2 'Stereo Speakers'
comment.item.3 'Stereo Speakers + Headphones'
comment.item.4 Headphones
iface MIXER
name 'Amp Mode'
value Off
}
control.90 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 Off
comment.item.1 'GSM Handset'
comment.item.2 'GSM Headset'
comment.item.3 'GSM Bluetooth'
comment.item.4 Speakers
comment.item.5 Headphones
comment.item.6 'Capture Handset'
comment.item.7 'Capture Headset'
comment.item.8 'Capture Bluetooth'
iface MIXER
name 'Neo Mode'
value 'GSM Bluetooth'
}
control.91 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 1
iface MIXER
name 'Amp Spk 3D Playback Switch'
value false
}
control.92 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 1
iface MIXER
name 'Amp HP 3d Playback Switch'
value false
}
control.93 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 1
iface MIXER
name 'Amp Fast Wakeup Playback Switch'
value false
}
control.94 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 1
iface MIXER
name 'Amp Earpiece 6dB Playback Switch'
value false
}
--
Jim Morris, http://blog.wolfman.com
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Jim Morris wrote: Jim Morris wrote: I am still trying to get a bluetooth headset to work with the GTA02. I found on the Wiki a pointer to this state file http://opensource.wolfsonmicro.com/~gg/neo1973/gsmbluetooth.state however it is gta01 specific, and around control 51, all the control numbers change as gta02 seems to have an additional control there. So I am slowly going through all the controls from 51 onwards and trying to see what changed between gta01 and gta02. By going through line by line I see the differences that the old gta01 state files had between bt and headset states, so fixing them up in a newer gta02 state file was ok until gta01 control 87 upwards. None of these controls appear in a gta02 state file, so there seems to be no equivalent settings. Especially control 90, which seems pretty important for bluetooth but has no equivalent in the gt02 state file. One thing that may help, is if someone could provide a mapping of the wolfson registers as documented in the WM8753L pdf to the alsa controls. Someone had to have written the code that twiddles the registers in that chip, and would know which also control matches which register. I looked at the obvious choice which would be a 1:1 mapping of also control number to register number, but that doesn't match even closely. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Jim Morris escreveu: One thing that may help, is if someone could provide a mapping of the wolfson registers as documented in the WM8753L pdf to the alsa controls. Someone had to have written the code that twiddles the registers in that chip, and would know which also control matches which register. That would be sound/soc/codecs/wm8753.c and sound/soc/s3c24xx/neo1973_gta02_wm8753.c on the kernel source code. Take a look: http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/codecs/wm8753.c;hb=stable http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/s3c24xx/neo1973_gta02_wm8753.c;hb=stable The mapping is there, you only have to find out how it's described. -- Cesar Eduardo Barros [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GsmBluetooth state file for gta02
Cesar Eduardo Barros wrote: Jim Morris escreveu: One thing that may help, is if someone could provide a mapping of the wolfson registers as documented in the WM8753L pdf to the alsa controls. Someone had to have written the code that twiddles the registers in that chip, and would know which also control matches which register. That would be sound/soc/codecs/wm8753.c and sound/soc/s3c24xx/neo1973_gta02_wm8753.c on the kernel source code. Take a look: http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/codecs/wm8753.c;hb=stable http://git.openmoko.org/?p=kernel.git;a=blob;f=sound/soc/s3c24xx/neo1973_gta02_wm8753.c;hb=stable The mapping is there, you only have to find out how it's described. Thanks for the pointers. Thats 2,000 lines of code that is about as clear as mud! (and I've written audio drivers before). There is no mention of Bluetooth in these drivers, and no indication how to switch into bluetooth mode. Obviously gta01 was very different, and it is not even clear that the gsmbluetooth.state even worked on a gta01, at least I've never seen any gta01 user claim they had it working. I really don't see how we are supposed to figure this stuff out, without any help from Openmoko. This is a core piece of functionality for a GSM phone guys! Especially in a state where handsfree devices are required whilst driving. I would appreciate a little help from Openmoko to provide a working example of routing the audio to/from a BT headset during a call. I think they may need some help from Wolfson to figure it out! As I said there seem to be no equivalent functions in gta02's alsa settings to match the ones in gta01 that were used to switch into BT mode. Thanks -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
