headers
Belisko Marek | 2 May 2011 09:56
Picon

Re: [bug] ASoC uda134x not working for me, and udev crashed at startup

CC also linux-sound mailing list.

On Mon, May 2, 2011 at 9:21 AM, microcai <microcaicai <at> gmail.com> wrote:
> Heya,
>
> The commit a110f4ef810ee29d810876df725f41d66629733e is not working for
> me. I'm using an TQ2440 platform, very similar to mini2440. Only the LCD
> and LED is the difference. Basically just copy & past from the
> mach-mini2440.c to mach-tq2440.c. ;)
>
> I installed Gentoo on the system, when startup, I got
>
> [    1.645000] ALSA device list:
> [    1.645000]   No soundcards found.
With this patch you shouldn't see this in boot log. At least it work for me ;)
>
>
> And when systemd starts udevadm, I got Unable to handle kernel paging
> request, complet list append.
>
> Please CC me if any one knows anything about it, or need more
> information. I'll be glad to provide help.
>
>
> [   20.455000] ------------[ cut here ]------------
> [   20.455000] WARNING: at fs/sysfs/file.c:355 sysfs_open_file+0xa4/0x268()
> [   20.460000] Unable to handle kernel paging request at virtual address
> 706f720
> [   20.460000] pgd = 82c70000
>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Belisko Marek | 3 May 2011 11:09
Picon

Re: [bug] ASoC uda134x not working for me, and udev crashed at startup

On Mon, May 2, 2011 at 9:56 AM, Belisko Marek <marek.belisko <at> gmail.com> wrote:
> CC also linux-sound mailing list.
>
> On Mon, May 2, 2011 at 9:21 AM, microcai <microcaicai <at> gmail.com> wrote:
>> Heya,
>>
>> The commit a110f4ef810ee29d810876df725f41d66629733e is not working for
>> me. I'm using an TQ2440 platform, very similar to mini2440. Only the LCD
>> and LED is the difference. Basically just copy & past from the
>> mach-mini2440.c to mach-tq2440.c. ;)
>>
>> I installed Gentoo on the system, when startup, I got
>>
>> [    1.645000] ALSA device list:
>> [    1.645000]   No soundcards found.
> With this patch you shouldn't see this in boot log. At least it work for me ;)
Did you enable Audio in menuconfig? For mini2440_defconfig audio is not selected
by default. SoC I2S Audio support UDA134X wired to a S3C24XX must be enabled.
Please let us know if it helps.
>>
>>
>> And when systemd starts udevadm, I got Unable to handle kernel paging
>> request, complet list append.
>>
>> Please CC me if any one knows anything about it, or need more
>> information. I'll be glad to provide help.
>>
>>
>> [   20.455000] ------------[ cut here ]------------
>> [   20.455000] WARNING: at fs/sysfs/file.c:355 sysfs_open_file+0xa4/0x268()
(Continue reading)

Permalink | Reply | 3 comments |
headers
microcai | 3 May 2011 13:46
Picon
Gravatar

Re: [bug] ASoC uda134x not working for me, and udev crashed at startup

 2011-05-03 17:09, Belisko Marek Wrote:
> On Mon, May 2, 2011 at 9:56 AM, Belisko Marek <marek.belisko <at> gmail.com> wrote:
>> CC also linux-sound mailing list.
>>
>> On Mon, May 2, 2011 at 9:21 AM, microcai <microcaicai <at> gmail.com> wrote:
>>> Heya,
>>>
>>> The commit a110f4ef810ee29d810876df725f41d66629733e is not working for
>>> me. I'm using an TQ2440 platform, very similar to mini2440. Only the LCD
>>> and LED is the difference. Basically just copy & past from the
>>> mach-mini2440.c to mach-tq2440.c. ;)
>>>
>>> I installed Gentoo on the system, when startup, I got
>>>
>>> [    1.645000] ALSA device list:
>>> [    1.645000]   No soundcards found.
>> With this patch you shouldn't see this in boot log. At least it work for me ;)
> Did you enable Audio in menuconfig? For mini2440_defconfig audio is not selected
> by default. SoC I2S Audio support UDA134X wired to a S3C24XX must be enabled.
> Please let us know if it helps.

Sure, how can't I even don't know this?
Older source code from manufacturer's website (They don't release patch,
but completely kernel tarbal, blame them. And not available for
download, only in DVD.)  don't even have s3c_source_dma and codex stuff,
but sound works. Strange. Since they don't release patch , I don't know
if they have patched the UDA134X driver.

diff shows much garbage even they declare that they use  2.6.30.4 kernel.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Belisko Marek | 3 May 2011 22:18
Picon

Re: [bug] ASoC uda134x not working for me, and udev crashed at startup

On Tue, May 3, 2011 at 1:46 PM, microcai <microcaicai <at> gmail.com> wrote:
>  2011-05-03 17:09, Belisko Marek Wrote:
>> On Mon, May 2, 2011 at 9:56 AM, Belisko Marek <marek.belisko <at> gmail.com> wrote:
>>> CC also linux-sound mailing list.
>>>
>>> On Mon, May 2, 2011 at 9:21 AM, microcai <microcaicai <at> gmail.com> wrote:
>>>> Heya,
>>>>
>>>> The commit a110f4ef810ee29d810876df725f41d66629733e is not working for
>>>> me. I'm using an TQ2440 platform, very similar to mini2440. Only the LCD
>>>> and LED is the difference. Basically just copy & past from the
>>>> mach-mini2440.c to mach-tq2440.c. ;)
>>>>
>>>> I installed Gentoo on the system, when startup, I got
>>>>
>>>> [    1.645000] ALSA device list:
>>>> [    1.645000]   No soundcards found.
>>> With this patch you shouldn't see this in boot log. At least it work for me ;)
>> Did you enable Audio in menuconfig? For mini2440_defconfig audio is not selected
>> by default. SoC I2S Audio support UDA134X wired to a S3C24XX must be enabled.
>> Please let us know if it helps.
Sorry confusing. Which kernel you're using? I use mainline kernel not some
custom tree. Please use mainline.
>
> Sure, how can't I even don't know this?
> Older source code from manufacturer's website (They don't release patch,
> but completely kernel tarbal, blame them. And not available for
> download, only in DVD.)  don't even have s3c_source_dma and codex stuff,
> but sound works. Strange. Since they don't release patch , I don't know
> if they have patched the UDA134X driver.
(Continue reading)

Permalink | Reply | 1 comment |
headers
@@@ | 11 May 2011 05:39
Picon

Can You Be Trusted?

 WILL EXECUTION!

 I wish to intimate you with a request that would be of immense benefit 
 to
 both of us. Being an executor of WILL, it is possible that we may be
 tempted to make fortune out of my client situation, when we cannot help
 it, or left with no better option.

 The issue I am presenting to you is about my client who WILLED a 
 fortune
 to his next-of-kin. It was most unfortunate that he and his next-of-kin
 died on the same day in the sharja plane crash of Tuesday 10 February
 2004. I am now faced with confusion of who to pass the fortune to.
 According to the English law, the fortune is supposed to be bequeathed 
 to
 the government. However, I don’t belong to that school of thought which
 proposes that the fortune of unlucky people be given to the government.
 I seek your assistance to act as the beneficiary of the inheritance, 
 and
 lay claim to the legacy(12.4million pounds sterling),which this my
 unfortunate client bequeathed to his next-of-kin. For now, it is
 only known to me, as my client has great confidence in me. Everything 
 will
 be left between you and I. The share would be 40% for you and 60% for
 me. All I have to do is to amend the WILL stating you as the 
 beneficiary
 to the 12.4million pounds sterling.

 I prefer not to divulge my full identity so as not to risk being 
 disbarred.
(Continue reading)

Permalink | Reply | 0 comments |
headers
@@@ | 30 May 2011 17:35
Picon

CAN I TRUST YOU

Hello, 

I am Capt. Sam Dennison, an officer of the U.S Army. I am on the move to 
Afghanistan from Iraq as the last batch just left and have some items I will need to 
ship to you. Can you be trusted? 
Please view this link:  http://news.bbc.co.uk/2/hi/7444083.stm

I will explain further when i get
a response from you.Contact me on email(cpt.samdennison <at> gmail.com)

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |

Gmane