* THANKS
@ 2005-03-02 21:45 Yoshinori K. Okuji
2005-03-08 20:47 ` THANKS Marco Gerards
0 siblings, 1 reply; 54+ messages in thread
From: Yoshinori K. Okuji @ 2005-03-02 21:45 UTC (permalink / raw)
To: grub-devel
The file THANKS hadn't been updated for a while, so I added some people
into it. In principle, we should add a person when he/she sends a piece
of code and/or document and we use it. Even if one does not send any
material, when you think he/she contributes significantly (such as
debugging tedious code), you should add him/her.
I hope I didn't forget to add anyone, but if I missed anyone, let me
know.
Okuji
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: THANKS
2005-03-02 21:45 THANKS Yoshinori K. Okuji
@ 2005-03-08 20:47 ` Marco Gerards
2005-03-08 22:49 ` THANKS Yoshinori K. Okuji
0 siblings, 1 reply; 54+ messages in thread
From: Marco Gerards @ 2005-03-08 20:47 UTC (permalink / raw)
To: The development of GRUB 2
"Yoshinori K. Okuji" <okuji@enbug.org> writes:
> The file THANKS hadn't been updated for a while, so I added some people
> into it. In principle, we should add a person when he/she sends a piece
> of code and/or document and we use it. Even if one does not send any
> material, when you think he/she contributes significantly (such as
> debugging tedious code), you should add him/her.
>
> I hope I didn't forget to add anyone, but if I missed anyone, let me
> know.
At least Guillem is missing. Do you want me to add him?
Thanks,
Marco
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
@ 2023-11-22 18:43 Tatyana Polunin
0 siblings, 0 replies; 54+ messages in thread
From: Tatyana Polunin @ 2023-11-22 18:43 UTC (permalink / raw)
To: git
Thanks!
^ permalink raw reply [flat|nested] 54+ messages in thread
* thanks
@ 2023-04-13 16:59 my email
0 siblings, 0 replies; 54+ messages in thread
From: my email @ 2023-04-13 16:59 UTC (permalink / raw)
To: util-linux
What command (and what procedure) to change the "max total shared memory" limit. I have used ipcs to obtain data but the shared memory limit is too high. Also possibly too high is the "max number of segments" Pls advise how to further limit. Suspected malware. Thanks.
Ipcs -u
max number of segments = 4096
max seg size (kbytes) = 18014398509465599
max total shared memory (kbytes) = 18446744073709551612
min seg size (bytes) = 1
No analytics, no ads, no tracking, no
sharing personal data.
No analytics, no ads, no tracking, no sharing personal data.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: [PATCH] docs: clarify that credential discards unrecognised attributes
@ 2022-10-24 23:59 Jeff King
2022-10-25 1:51 ` Thanks M Hickford
0 siblings, 1 reply; 54+ messages in thread
From: Jeff King @ 2022-10-24 23:59 UTC (permalink / raw)
To: M Hickford via GitGitGadget; +Cc: git, M Hickford
On Mon, Oct 24, 2022 at 07:57:48AM +0000, M Hickford via GitGitGadget wrote:
> It was previously unclear how unrecognised attributes are handled.
Yeah, this was always part of the intended behavior, but I agree we did
not say it very explicitly (aside from an in-code comment!). Both the
intent and content of your patch look good to me.
We did discuss patches a long time ago that would let Git carry
arbitrary keys between helpers, even if Git itself didn't understand it.
One of the intended uses was to let helpers talk to each other about
TTLs. So if you had say:
[credential]
helper = generate-some-token
helper = cache
where the first helper generates a token, and the second caches it, the
first one could shove a "ttl" or "expiration" key into the protocol,
which the cache could then learn to respect.
But we never merged such a thing, and in practice I think people would
just implement both parts as a single helper for simplicity. And anyway,
even if we did want to do that, such a patch would want to modify the
documentation to explain the new behavior. :)
-Peff
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
2022-10-24 23:59 [PATCH] docs: clarify that credential discards unrecognised attributes Jeff King
@ 2022-10-25 1:51 ` M Hickford
2022-10-25 9:05 ` Thanks Bagas Sanjaya
0 siblings, 1 reply; 54+ messages in thread
From: M Hickford @ 2022-10-25 1:51 UTC (permalink / raw)
To: peff; +Cc: git, gitgitgadget, mirth.hickford
Thanks Jeff for your reply. This is helpful to understand the background.
(first message using git send-email, hopefully I followed the instructions correctly)
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
2022-10-25 1:51 ` Thanks M Hickford
@ 2022-10-25 9:05 ` Bagas Sanjaya
2022-10-26 4:39 ` Thanks M Hickford
0 siblings, 1 reply; 54+ messages in thread
From: Bagas Sanjaya @ 2022-10-25 9:05 UTC (permalink / raw)
To: M Hickford, peff; +Cc: git, gitgitgadget
On 10/25/22 08:51, M Hickford wrote:
> Thanks Jeff for your reply. This is helpful to understand the background.
>
> (first message using git send-email, hopefully I followed the instructions correctly)
You messed up the thread (you broke it).
On every message showed on lore.kernel.org/git, there is reply
instructions at the bottom of the message's page. Follow it closely.
If you insisted on either using git-send-email(1) or mailto: link
to reply, you need to manually quote any portion of original message
you wish to give the context. Make sure every line of quoted text
starts with `> `.
Better yet, reply using "reply-all" button or key in your mail client.
However, make sure your email is text/plain (not HTML) and your mail
client doesn't mess up with whitespaces (convert tabs to spaces,
word wrapping).
Thanks.
--
An old man doll... just what I always wanted! - Clara
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
2022-10-25 9:05 ` Thanks Bagas Sanjaya
@ 2022-10-26 4:39 ` M Hickford
2022-10-26 5:18 ` Thanks Jeff King
2022-10-26 9:36 ` Thanks Junio C Hamano
0 siblings, 2 replies; 54+ messages in thread
From: M Hickford @ 2022-10-26 4:39 UTC (permalink / raw)
To: bagasdotme; +Cc: git, mirth.hickford
> > (first message using git send-email, hopefully I followed the instructions correctly)
>
> You messed up the thread (you broke it).
Curious. The thread overview "5+ messages" at https://lore.kernel.org/git/20221025015116.4730-1-mirth.hickford@gmail.com/#related looks okay to me. I followed the git send-email instructions setting the In-Reply-To header. I changed the subject -- maybe that confused some clients? Thanks for the tips.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
2022-10-26 4:39 ` Thanks M Hickford
@ 2022-10-26 5:18 ` Jeff King
2022-10-26 9:36 ` Thanks Junio C Hamano
1 sibling, 0 replies; 54+ messages in thread
From: Jeff King @ 2022-10-26 5:18 UTC (permalink / raw)
To: M Hickford; +Cc: bagasdotme, git
On Wed, Oct 26, 2022 at 05:39:05AM +0100, M Hickford wrote:
> > > (first message using git send-email, hopefully I followed the instructions correctly)
> >
> > You messed up the thread (you broke it).
>
> Curious. The thread overview "5+ messages" at
> https://lore.kernel.org/git/20221025015116.4730-1-mirth.hickford@gmail.com/#related
> looks okay to me. I followed the git send-email instructions setting
> the In-Reply-To header. I changed the subject -- maybe that confused
> some clients?
Your reply looked fine to me. The in-reply-to you used is correct. It's
OK to change the subject (though usually only done when the conversation
drifts to a different topic).
-Peff
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
2022-10-26 4:39 ` Thanks M Hickford
2022-10-26 5:18 ` Thanks Jeff King
@ 2022-10-26 9:36 ` Junio C Hamano
1 sibling, 0 replies; 54+ messages in thread
From: Junio C Hamano @ 2022-10-26 9:36 UTC (permalink / raw)
To: M Hickford; +Cc: bagasdotme, git
M Hickford <mirth.hickford@gmail.com> writes:
>> > (first message using git send-email, hopefully I followed the instructions correctly)
>>
>> You messed up the thread (you broke it).
>
> Curious. The thread overview "5+ messages" at
> https://lore.kernel.org/git/20221025015116.4730-1-mirth.hickford@gmail.com/#related
> looks okay to me. I followed the git send-email instructions
> setting the In-Reply-To header. I changed the subject -- maybe
> that confused some clients? Thanks for the tips.
Your In-Reply-To: header looked OK to me. Some webmail platforms
break the thread when Subject: is edited, but that is their bug. As
long as you keep the In-Reply-To: chain correct, retitling the
message as necessary is indeed encouraged practice.
^ permalink raw reply [flat|nested] 54+ messages in thread
* THANKS
@ 2015-08-15 21:23 Rosie EBe Arthur
0 siblings, 0 replies; 54+ messages in thread
From: Rosie EBe Arthur @ 2015-08-15 21:23 UTC (permalink / raw)
My name is Rosie Ebe Arthur, From Accra Ghana.Head, Human Resources
staff of Standard Chartered Bank Ghana,I have A business proposal of
(US$3,350,000.00), for you from my Bank which I need your co-operation
as my partner to transfer this Money to your bank account within Five
(5) working days. This transaction is legal without any problem and it
is bank to bank transfer and 100% risk free.
As soon as the three Million three Hundred and Fifty Thousand Dollars
[$3,350.000.00]is transferred to your bank account, you shall take
40%, while I take 60%. If you are interested to work with me reply my
email so I can send you more details. And I can provide any needed
document during the transfer.
^ permalink raw reply [flat|nested] 54+ messages in thread
* THANKS
@ 2015-07-27 9:51 Rosie EBe Arthur
0 siblings, 0 replies; 54+ messages in thread
From: Rosie EBe Arthur @ 2015-07-27 9:51 UTC (permalink / raw)
My name is Rosie Ebe Arthur, From Accra Ghana.Head, Human Resources staff of
Standard Chartered Bank Ghana,I have A business proposal of
(US$2,350,000.00), for
you from my Bank which I need your co-operation as my partner to transfer this
Money to your bank account within Five (5) working days. This
transaction is legal
without any problem and it is bank to bank transfer and 100% risk free.
As soon as the Seven Million three Hundred and Fifty Thousand Dollars
[$7,350.000.00]is transferred to your bank account, you shall take 40%, while I
take 60%. If you are interested to work with me reply my email so I
can send you
more details. And I can provide any needed document during the transfer.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
@ 2015-07-23 22:52 bbaumann
0 siblings, 0 replies; 54+ messages in thread
From: bbaumann @ 2015-07-23 22:52 UTC (permalink / raw)
To: r.gsvaso@yandex.com
Hi,
I've an offer for you.
^ permalink raw reply [flat|nested] 54+ messages in thread
* THANKS
@ 2015-06-28 4:38 Rosie EBe Arthur
0 siblings, 0 replies; 54+ messages in thread
From: Rosie EBe Arthur @ 2015-06-28 4:38 UTC (permalink / raw)
My name is Rosie Ebe Arthur, From Accra Ghana.Head, Human Resources
staff of Standard Chartered Bank Ghana,I have A business proposal of
(US$7,350,000.00), for you from my Bank which I need your co-operation
as my partner to transfer this Money to your bank account within Five
(5) working days. This transaction is legal without any problem and it
is bank to bank transfer and 100% risk free.
As soon as the Seven Million three Hundred and Fifty Thousand Dollars
[$7,350.000.00]is transferred to your bank account, you shall take
40%, while I take 60%. If you are interested to work with me reply my
email so I can send you more details. And I can provide any needed
document during the transfer.
^ permalink raw reply [flat|nested] 54+ messages in thread
* THANKS
@ 2015-05-23 23:03 STEVE KOFFI
0 siblings, 0 replies; 54+ messages in thread
From: STEVE KOFFI @ 2015-05-23 23:03 UTC (permalink / raw)
Mr. Steve Koffi, From Tema Ghana staff of Standard Chartered Bank
Ghana,I have A business proposal of (US$4,450,000.00), for you from my
Bank which I need your co-operation as my partner to transfer this
Money to your bank account within Five (5) working days. This
transaction is legal without any problem and it is bank to bank
transfer and 100% risk free.
As soon as the four Million four Hundred and Fifty Thousand Dollar
[$4,450.000.00]is transferred to your bank account, you shall take
40%, while I take 60%. If you are interested to work with me reply my
email so I can send you more details. And I can provide any needed
document during the transfer.
^ permalink raw reply [flat|nested] 54+ messages in thread
* THANKS
@ 2012-06-04 4:54 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2012-06-04 4:54 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together in transferring $19,500,000.USD from my bank. Finally if you are interested I shall provide you with more details. my private Email: mr.songlile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks.
@ 2012-04-24 8:27 Simon O'Riordan
0 siblings, 0 replies; 54+ messages in thread
From: Simon O'Riordan @ 2012-04-24 8:27 UTC (permalink / raw)
To: kvm
To Gert Hoffman for fixing the USB in 1.0.1 Qemu-kvm.
Simon
--------------------------------------------------------------------------------------------------
This email and any attachments are confidential and are for the use of the addressee only. If you are not the addressee, you must not use or disclose the contents to any other person. Please immediately notify the sender and delete the email. Statements and opinions expressed here may not represent those of the company. Email correspondence is monitored by the company. This information may be subject to export control regulation. You are obliged to comply with such regulations.
Renishaw plc (company number 1106260), Wotton Travel Limited (company number 01973158) and Renishaw Advanced Materials Limited (company number 04632041), are companies registered in England and Wales with a registered office at New Mills, Wotton-under-Edge, Gloucestershire, GL12 8JR, United Kingdom, Telephone +44 1453 524524.
--------------------------------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
@ 2012-04-24 8:25 Simon O'Riordan
0 siblings, 0 replies; 54+ messages in thread
From: Simon O'Riordan @ 2012-04-24 8:25 UTC (permalink / raw)
To: kvm
To Gert Hoffman for fixing the USB in 1.0.1 Qemu-kvm
S.J.P.O'Riordan
Software Engineer,
MAPD Renishaw
Tel.01453 523701
--------------------------------------------------------------------------------------------------
This email and any attachments are confidential and are for the use of the addressee only. If you are not the addressee, you must not use or disclose the contents to any other person. Please immediately notify the sender and delete the email. Statements and opinions expressed here may not represent those of the company. Email correspondence is monitored by the company. This information may be subject to export control regulation. You are obliged to comply with such regulations.
Renishaw plc (company number 1106260), Wotton Travel Limited (company number 01973158) and Renishaw Advanced Materials Limited (company number 04632041), are companies registered in England and Wales with a registered office at New Mills, Wotton-under-Edge, Gloucestershire, GL12 8JR, United Kingdom, Telephone +44 1453 524524.
--------------------------------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
@ 2011-12-13 23:47 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-12-13 23:47 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together in transferring $19,500,000.USD from my bank. Finally if you are interested I shall provide you with more details. my private Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
@ 2011-12-13 23:44 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-12-13 23:44 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together in transferring $19,500,000.USD from my bank. Finally if you are interested I shall provide you with more details. my private Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
@ 2011-12-02 3:58 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-12-02 3:58 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together in transferring $19,500,000.USD from my bank. Finally if you are interested I shall provide you with more details. my private Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
@ 2011-12-02 3:29 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-12-02 3:29 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together in transferring $19,500,000.USD from my bank. Finally if you are interested I shall provide you with more details. my private Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
@ 2011-12-02 3:29 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-12-02 3:29 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together in transferring $19,500,000.USD from my bank. Finally if you are interested I shall provide you with more details. my private Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: THANKS
@ 2011-11-22 6:38 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-11-22 6:38 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together in transferring $19,500,000.USD from my bank. Finally if you are interested I shall provide you with more details. my private Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: THANKS
@ 2011-11-22 5:22 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-11-22 5:22 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work together in transferring $19,500,000.USD from my bank. Finally if you are interested I shall provide you with more details. my private Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
@ 2011-09-28 7:51 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-09-28 7:51 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work
together in transferring $19,500,000.USD from my bank.
Finally if you are interested I shall provide you with more details.
Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
@ 2011-09-28 7:51 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-09-28 7:51 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work
together in transferring $19,500,000.USD from my bank.
Finally if you are interested I shall provide you with more details.
Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
@ 2011-09-28 7:03 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-09-28 7:03 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work
together in transferring $19,500,000.USD from my bank.
Finally if you are interested I shall provide you with more details.
Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
@ 2011-09-28 5:45 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-09-28 5:45 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work
together in transferring $19,500,000.USD from my bank.
Finally if you are interested I shall provide you with more details.
Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
@ 2011-08-28 4:34 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-08-28 4:34 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work
together in transferring $19,500,000.USD from my bank.
Finally if you are interested I shall provide you with more details.
Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
@ 2011-08-28 3:49 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-08-28 3:49 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work
together in transferring $19,500,000.USD from my bank.
Finally if you are interested I shall provide you with more details.
Email: mrsong.lile@yahoo.cn
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
@ 2011-08-15 12:55 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-08-15 12:55 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work
together in transferring $19,500,000.USD from my bank to you account.
Finally if you are interested I shall provide you with more details.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
@ 2011-08-15 12:13 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-08-15 12:13 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work
together in transferring $19,500,000.USD from my bank to you account.
Finally if you are interested I shall provide you with more details.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
@ 2011-08-15 12:13 Song Li
0 siblings, 0 replies; 54+ messages in thread
From: Song Li @ 2011-08-15 12:13 UTC (permalink / raw)
To: Recipients
l am a Staff of Hang Seng Bank HongKong, I do not know if we can work
together in transferring $19,500,000.USD from my bank to you account.
Finally if you are interested I shall provide you with more details.
^ permalink raw reply [flat|nested] 54+ messages in thread
* thanks
@ 2010-09-03 21:49 Mrs Riza Perla
0 siblings, 0 replies; 54+ messages in thread
From: Mrs Riza Perla @ 2010-09-03 21:49 UTC (permalink / raw)
Good day,
I would like to discuss a $10.2Million US Dollars business proposal with you. My
personal email: (mrsrizap1962@yahoo.com). Hope to hear from you soon.
Kind Regards,
Mrs. Riza Perla.
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
@ 2010-06-01 8:26 Dennis Don
0 siblings, 0 replies; 54+ messages in thread
From: Dennis Don @ 2010-06-01 8:26 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 125 bytes --]
My Dear,
Find and read attachment carefully as it has been scan against virus.
Regards
MR.DENNIS DON
Tele: +27 715260050
[-- Attachment #2: MR[1].DENNIS DON.jpg --]
[-- Type: image/jpeg, Size: 122587 bytes --]
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
@ 2009-01-02 16:53 jimmy liu
0 siblings, 0 replies; 54+ messages in thread
From: jimmy liu @ 2009-01-02 16:53 UTC (permalink / raw)
To: linuxppc-dev
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: thanks
@ 2006-11-24 13:15 amit
0 siblings, 0 replies; 54+ messages in thread
From: amit @ 2006-11-24 13:15 UTC (permalink / raw)
To: oswin
[-- Attachment #1.1.1: Type: text/plain, Size: 3237 bytes --]
----- Original Message -----
From: nfs@lists.sourceforge.net
To: perkasamnck@infobroker.com
Sent: Saturday, November 18, 2006 9:39 AM
Subject: thanks
power to move. There I couch when owls do cry.venturous fairy shall seek the squirrel's hoard, and fetch you some
his fair lady yet he complained of the interval being tedious, aslike one dead before him, wishing she might never more open her eyes.cheered his sister with pleasant speeches, and happy remarks, all the
to these kind words, telling them she would lodge them in her bosom as
Valentine introduced him to Silvia, saying, Sweet lady, entertain himbrought letters from Bellario of advice how to proceed, and also everybracelet on the arm of his wife, which he begged she would preservetorture if he did not confess how he came by the diamond ring on his
and kind. And he said that rather than return to Gonerill, with halfthan a poor Bedlambeggar, who had crept into this deserted hovel forwould be disclosed, in great haste dismissed the guests, excusing the
should pursue. If Helena wondered not, she grieved, when she found
should pursue. If Helena wondered not, she grieved, when she foundserious business he came about and his servant and the very horseshe continued, See where she comes, and brings your froward wives asDromios both so exactly alike, he at once conjectured aright of these
you must not speak. And have you nuns no farther privileges saidgrief and shame to utter. Angelo would not but by my yielding to histhan himself, and of a man's dark complexion but Viola secretly meant
Smooth, smiling parasites, destroyers under the mask of courtesy,
had their toes unplagued with corns would dance with them. And the oldcondemned by the laws of Verona to die if he were found within theto walk and it being a cold night, and the air unusually raw andletters, and skilfully erasing his own name, he in the stead of it
into favour.After that tempestuous night when Thaisa was thrown into the sea, andwho had restored Thaisa, the wife of Pericles, to life and Thaisa,
they found in that place, fell to eating and drinking, forgetful of
go he said, O thou most erring of the sons of men! knowest thou By those high issues that the s ordain'dcontent themselves with such food as Circe had stowed their vesselMeantime Minerva designing an interview between the king's daughter of
him to leave that abject station which he had assumed, placed him nextwith my sufferings, for with the inclement night, and the wet of theof some one who might assist us in this undertaking.
sit and please me with your speech, my ears would never let my eyes
indulgence, to relate either all, or any part of the events ofand there I saw fine gilt covers and gay pictures all fluttering
Grandmamma's violets were certainly best of all, but they never wentitself. It is true I had a few scruples, that it might, should itmortifications I so much dreaded therefore I endeavoured to submit
little while every day in some book that she might think proper to
curtain would draw up to the sound of soft music, and I should hear aevil that could have befallen me for I remembered how often I haddo not remember the events of the voyage in any order, was Atkinson
[-- Attachment #1.1.2: Type: text/html, Size: 4325 bytes --]
[-- Attachment #1.2: n8s3O5uGPM.gif --]
[-- Type: image/gif, Size: 16611 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: debugging nm256: some results, many questions
@ 2006-03-13 6:46 Florian Schlichting
2006-03-13 11:58 ` Takashi Iwai
0 siblings, 1 reply; 54+ messages in thread
From: Florian Schlichting @ 2006-03-13 6:46 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
[-- Attachment #1.1: Type: text/plain, Size: 1133 bytes --]
I went ahead implementing caching of reads to the ac97 mixer registers
inside the nm256 driver, and also included "preloading" of the cache,
just as the OSS driver does. And it works like a charm: no reads to the
mixers, no crashes any more!
Alas, this improvement has taught me what some of the reads were for -
detection of volume resolution, for example: I suddenly had two maxima
on the PCM mixer. As all my mixers have a resolution of 31, I customized
the values being written to the cache so that the ac97_codec would
"detect" the correct value. Now the only difference to the non-patched
state (according to alsactl) is that a few mixers are stereo instead of
mono - but up to now this doesn't seem to have any effect on anything I
do, everything works fine...
The question is: how portable is this to other users of nm256? Will we
need a detect for this workaround?
I've attached a patch against 1.0.10rc3 - I just saw that in 1.0.11rc3
there has been a cleanup in nm256, and my patch doesn't apply cleanly
any more... although I don't think it will need to be changed. Perhaps I
could have some feedback first?
Florian
[-- Attachment #1.2: nm256-patch --]
[-- Type: text/plain, Size: 3404 bytes --]
--- /usr/src/linux/sound/pci/nm256/nm256.c.orig 2006-03-13 13:46:23.000000000 +0800
+++ /usr/src/linux/sound/pci/nm256/nm256.c.cleaned_up 2006-03-13 14:13:28.000000000 +0800
@@ -1152,22 +1152,33 @@
}
/*
+ * some nm256 easily crash when reading from mixer registers
+ * thus we're caching both read and written values for reading
*/
static unsigned short
snd_nm256_ac97_read(ac97_t *ac97, unsigned short reg)
{
nm256_t *chip = ac97->private_data;
- int res;
if (reg >= 128)
return 0;
if (! snd_nm256_ac97_ready(chip))
return 0;
- res = snd_nm256_readw(chip, chip->mixer_base + reg);
+
+ if (! test_bit(reg, ac97->reg_accessed)) { /* ! read_workaround && */
+ /* we should never get here, really, as all regs have been
+ * loaded into the cache, and the cached-flags in reg_accessed
+ * are never cleared. Thus we could also test for
+ * ! read_workaround (once introduced and properly set)
+ */
+ ac97->regs[reg] = snd_nm256_readw(chip, chip->mixer_base + reg);
+ set_bit(reg, ac97->reg_accessed);
+ }
+
/* Magic delay. Bleah yucky. */
msleep(1);
- return res;
+ return ac97->regs[reg];
}
/*
@@ -1188,17 +1199,62 @@
while (tries-- > 0) {
snd_nm256_writew(chip, base + reg, val);
msleep(1); /* a little delay here seems better.. */
- if (snd_nm256_ac97_ready(chip))
+ if (snd_nm256_ac97_ready(chip)) {
+ /* successful write: set cache */
+ ac97->regs[reg] = (val & 0xdfdf); /* we don't do this volume resolution */
+ set_bit(reg, ac97->reg_accessed);
return;
+ }
}
snd_printd("nm256: ac97 codec not ready..\n");
}
+/*
+ * below copied from OSS driver
+ * this list could perhaps be fused with mixer_regs[] ??
+ *
+ * Initial register values to be written to the AC97 mixer.
+ * While most of these are identical to the reset values, we do this
+ * so that we have most of the register contents cached--this avoids
+ * reading from the mixer directly (which seems to be problematic,
+ * probably due to ignorance).
+ */
+
+struct initialValues
+{
+ unsigned int reg;
+ unsigned short value;
+};
+
+static struct initialValues nm256_ac97_initial_values[] =
+{
+ { AC97_MASTER, 0x8000 },
+ { AC97_HEADPHONE, 0x8000 },
+ { AC97_MASTER_MONO, 0x0000 },
+ { AC97_PC_BEEP, 0x0000 },
+ { AC97_PHONE, 0x0008 },
+ { AC97_MIC, 0x8000 },
+ { AC97_LINE, 0x8808 },
+ { AC97_CD, 0x8808 },
+ { AC97_VIDEO, 0x8808 },
+ { AC97_AUX, 0x8808 },
+ { AC97_PCM, 0x0808 },
+ { AC97_REC_SEL, 0x0000 },
+ { AC97_REC_GAIN, 0x0B0B },
+ { AC97_GENERAL_PURPOSE, 0x0000 },
+ { AC97_3D_CONTROL, 0x8000 },
+ { AC97_VENDOR_ID1, 0x8384 },
+ { AC97_VENDOR_ID2, 0x7609 },
+ { 0xffff, 0xffff }
+};
+
+
/* initialize the ac97 into a known state */
static void
snd_nm256_ac97_reset(ac97_t *ac97)
{
nm256_t *chip = ac97->private_data;
+ int x;
/* Reset the mixer. 'Tis magic! */
snd_nm256_writeb(chip, 0x6c0, 1);
@@ -1211,6 +1267,12 @@
snd_nm256_writeb(chip, 0x6cc, 0x80);
snd_nm256_writeb(chip, 0x6cc, 0x0);
}
+ for (x = 0; nm256_ac97_initial_values[x].reg != 0xffff; x++) {
+ /* preload the cache, so as to avoid even a single read of the mixer regs */
+ snd_ac97_write_cache(ac97,
+ nm256_ac97_initial_values[x].reg,
+ nm256_ac97_initial_values[x].value);
+ }
}
/* create an ac97 mixer interface */
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: debugging nm256: some results, many questions
2006-03-13 6:46 debugging nm256: some results, many questions Florian Schlichting
@ 2006-03-13 11:58 ` Takashi Iwai
2006-03-13 14:55 ` Florian Schlichting
0 siblings, 1 reply; 54+ messages in thread
From: Takashi Iwai @ 2006-03-13 11:58 UTC (permalink / raw)
To: Florian Schlichting; +Cc: alsa-devel
At Mon, 13 Mar 2006 14:46:28 +0800,
Florian Schlichting wrote:
>
> I went ahead implementing caching of reads to the ac97 mixer registers
> inside the nm256 driver, and also included "preloading" of the cache,
> just as the OSS driver does. And it works like a charm: no reads to the
> mixers, no crashes any more!
Great, thanks for nailing it down.
> Alas, this improvement has taught me what some of the reads were for -
> detection of volume resolution, for example: I suddenly had two maxima
> on the PCM mixer. As all my mixers have a resolution of 31, I customized
> the values being written to the cache so that the ac97_codec would
> "detect" the correct value. Now the only difference to the non-patched
> state (according to alsactl) is that a few mixers are stereo instead of
> mono - but up to now this doesn't seem to have any effect on anything I
> do, everything works fine...
>
> The question is: how portable is this to other users of nm256? Will we
> need a detect for this workaround?
I don't think so. The read cache should work in general.
> I've attached a patch against 1.0.10rc3 - I just saw that in 1.0.11rc3
> there has been a cleanup in nm256, and my patch doesn't apply cleanly
> any more... although I don't think it will need to be changed. Perhaps I
> could have some feedback first?
The writes in snd_nm256_ac97_reset() break the PM resume. You should
check reg_accessed[] and use the cached value if already written.
Also, it's simpler to call snd_nm256_ac97_write() directly there
instead of snd_ac97_write_cache().
Additionally, we may use a static resolution table to skip the volume
resolution detection with the latest ac97_codec.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: debugging nm256: some results, many questions
2006-03-13 11:58 ` Takashi Iwai
@ 2006-03-13 14:55 ` Florian Schlichting
2006-03-13 15:50 ` Takashi Iwai
0 siblings, 1 reply; 54+ messages in thread
From: Florian Schlichting @ 2006-03-13 14:55 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
On Mon, Mar 13, 2006 at 12:58:46PM +0100, Takashi Iwai wrote:
>
> The writes in snd_nm256_ac97_reset() break the PM resume. You should
> check reg_accessed[] and use the cached value if already written.
Yes, I just noticed the broken PM resume... The following is just to
check that I don't misunderstand things:
I originally wanted to write the initial values in snd_nm256_mixer(),
but there ac97 is still an ac97_template_t and doesn't have a register
cache. Still, reg_accessed[] is set there, meaning "register may be
touched". Consequently, in snd_nm256_ac97_reset() all usable
reg_accessed[] are already set, which the first time means nothing (and
all registers should be written), but during a resume means the value
shouldn't be touched... So there needs to be another way to distinguish
between these two states.
(I couldn't find any documentation about reg_accessed[], which to me
seems to indicate both "register can be accessed" and later "register
value is cached" - which really are two different things and I wonder
whether they should be kept apart?)
Assuming that when first initialized, all cache registers are set to
0x0000, which is also a valid volume setting, I could probably test for
a non-zero value in AC97_VENDOR_ID1, which would mean I've already done
the initial writing to the cache and it's a resume; otherwise all
registers are to be written.
> Additionally, we may use a static resolution table to skip the volume
> resolution detection with the latest ac97_codec.
I couldn't find any indication of that in 1.0.11rc3. Can you give me a
hint?
Florian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: debugging nm256: some results, many questions
2006-03-13 14:55 ` Florian Schlichting
@ 2006-03-13 15:50 ` Takashi Iwai
2006-03-14 19:59 ` Florian Schlichting
0 siblings, 1 reply; 54+ messages in thread
From: Takashi Iwai @ 2006-03-13 15:50 UTC (permalink / raw)
To: Florian Schlichting; +Cc: alsa-devel
At Mon, 13 Mar 2006 22:55:34 +0800,
Florian Schlichting wrote:
>
> On Mon, Mar 13, 2006 at 12:58:46PM +0100, Takashi Iwai wrote:
> >
> > The writes in snd_nm256_ac97_reset() break the PM resume. You should
> > check reg_accessed[] and use the cached value if already written.
>
> Yes, I just noticed the broken PM resume... The following is just to
> check that I don't misunderstand things:
>
> I originally wanted to write the initial values in snd_nm256_mixer(),
> but there ac97 is still an ac97_template_t and doesn't have a register
> cache. Still, reg_accessed[] is set there, meaning "register may be
> touched". Consequently, in snd_nm256_ac97_reset() all usable
> reg_accessed[] are already set, which the first time means nothing (and
> all registers should be written), but during a resume means the value
> shouldn't be touched... So there needs to be another way to distinguish
> between these two states.
>
> (I couldn't find any documentation about reg_accessed[], which to me
> seems to indicate both "register can be accessed" and later "register
> value is cached" - which really are two different things and I wonder
> whether they should be kept apart?)
Well, practically this check is used only by NM256, so it's OK to
change that interface.
IMO, we can implement the filtering more cleanly in the accessor side,
i.e. filtering the register in snd_nm256_ac97_read/write. In that
way, we can clean up ac97_code.c, too.
How about the patch below? (It's only for CVS version)
> Assuming that when first initialized, all cache registers are set to
> 0x0000, which is also a valid volume setting, I could probably test for
> a non-zero value in AC97_VENDOR_ID1, which would mean I've already done
> the initial writing to the cache and it's a resume; otherwise all
> registers are to be written.
>
> > Additionally, we may use a static resolution table to skip the volume
> > resolution detection with the latest ac97_codec.
>
> I couldn't find any indication of that in 1.0.11rc3. Can you give me a
> hint?
It's newly added in the CVS version. Look at
ac97_patch.c:patch_lm4550()
Takashi
Index: alsa-kernel/include/ac97_codec.h
===================================================================
RCS file: /home/iwai/cvs/alsa/alsa-kernel/include/ac97_codec.h,v
retrieving revision 1.75
diff -u -r1.75 ac97_codec.h
--- alsa-kernel/include/ac97_codec.h 9 Feb 2006 11:43:01 -0000 1.75
+++ alsa-kernel/include/ac97_codec.h 13 Mar 2006 15:49:22 -0000
@@ -433,6 +433,12 @@
struct snd_info_entry *proc;
};
+/* static resolution table */
+struct snd_ac97_res_table {
+ unsigned short reg; /* register */
+ unsigned short bits; /* resolution bitmask */
+};
+
struct snd_ac97_template {
void *private_data;
void (*private_free) (struct snd_ac97 *ac97);
@@ -440,14 +446,7 @@
unsigned short num; /* number of codec: 0 = primary, 1 = secondary */
unsigned short addr; /* physical address of codec [0-3] */
unsigned int scaps; /* driver capabilities */
- unsigned int limited_regs; /* allow limited registers only */
- DECLARE_BITMAP(reg_accessed, 0x80); /* bit flags */
-};
-
-/* static resolution table */
-struct snd_ac97_res_table {
- unsigned short reg; /* register */
- unsigned short bits; /* resolution bitmask */
+ const struct snd_ac97_res_table *res_table; /* static resolution */
};
struct snd_ac97 {
@@ -476,7 +475,6 @@
unsigned int rates[6]; /* see AC97_RATES_* defines */
unsigned int spdif_status;
unsigned short regs[0x80]; /* register cache */
- unsigned int limited_regs; /* allow limited registers only */
DECLARE_BITMAP(reg_accessed, 0x80); /* bit flags */
union { /* vendor specific code */
struct {
Index: alsa-kernel/pci/ac97/ac97_codec.c
===================================================================
RCS file: /home/iwai/cvs/alsa/alsa-kernel/pci/ac97/ac97_codec.c,v
retrieving revision 1.202
diff -u -r1.202 ac97_codec.c
--- alsa-kernel/pci/ac97/ac97_codec.c 9 Feb 2006 11:46:47 -0000 1.202
+++ alsa-kernel/pci/ac97/ac97_codec.c 13 Mar 2006 15:49:22 -0000
@@ -192,9 +192,6 @@
static int snd_ac97_valid_reg(struct snd_ac97 *ac97, unsigned short reg)
{
- if (ac97->limited_regs && ! test_bit(reg, ac97->reg_accessed))
- return 0;
-
/* filter some registers for buggy codecs */
switch (ac97->id) {
case AC97_ID_AK4540:
@@ -1008,9 +1005,6 @@
break;
}
- if (ac97->limited_regs && test_bit(reg, ac97->reg_accessed))
- return 1; /* allow without check */
-
val = snd_ac97_read(ac97, reg);
if (!(val & mask)) {
/* nothing seems to be here - mute flag is not set */
@@ -1866,8 +1860,7 @@
ac97->num = template->num;
ac97->addr = template->addr;
ac97->scaps = template->scaps;
- ac97->limited_regs = template->limited_regs;
- memcpy(ac97->reg_accessed, template->reg_accessed, sizeof(ac97->reg_accessed));
+ ac97->res_table = template->res_table;
bus->codec[ac97->num] = ac97;
mutex_init(&ac97->reg_mutex);
mutex_init(&ac97->page_mutex);
Index: alsa-kernel/pci/nm256/nm256.c
===================================================================
RCS file: /home/iwai/cvs/alsa/alsa-kernel/pci/nm256/nm256.c,v
retrieving revision 1.81
diff -u -r1.81 nm256.c
--- alsa-kernel/pci/nm256/nm256.c 16 Jan 2006 16:40:06 -0000 1.81
+++ alsa-kernel/pci/nm256/nm256.c 13 Mar 2006 15:49:22 -0000
@@ -228,6 +228,7 @@
unsigned int use_cache: 1; /* use one big coef. table */
unsigned int reset_workaround: 1; /* Workaround for some laptops to avoid freeze */
unsigned int reset_workaround_2: 1; /* Extended workaround for some other laptops to avoid freeze */
+ unsigned int in_resume: 1;
int mixer_base; /* register offset of ac97 mixer */
int mixer_status_offset; /* offset of mixer status reg. */
@@ -242,6 +243,7 @@
struct nm256_stream streams[2];
struct snd_ac97 *ac97;
+ DECLARE_BITMAP(allowed_regs, 128);
struct snd_pcm *pcm;
@@ -1154,22 +1156,17 @@
}
/*
+ * some nm256 easily crash when reading from mixer registers
+ * thus we're caching both read and written values for reading
*/
static unsigned short
snd_nm256_ac97_read(struct snd_ac97 *ac97, unsigned short reg)
{
struct nm256 *chip = ac97->private_data;
- int res;
- if (reg >= 128)
+ if (! test_bit(reg, chip->allowed_regs))
return 0;
-
- if (! snd_nm256_ac97_ready(chip))
- return 0;
- res = snd_nm256_readw(chip, chip->mixer_base + reg);
- /* Magic delay. Bleah yucky. */
- msleep(1);
- return res;
+ return ac97->regs[reg];
}
/*
@@ -1182,6 +1179,9 @@
int tries = 2;
u32 base;
+ if (! test_bit(reg, chip->allowed_regs))
+ return;
+
base = chip->mixer_base;
snd_nm256_ac97_ready(chip);
@@ -1190,12 +1190,71 @@
while (tries-- > 0) {
snd_nm256_writew(chip, base + reg, val);
msleep(1); /* a little delay here seems better.. */
- if (snd_nm256_ac97_ready(chip))
+ if (snd_nm256_ac97_ready(chip)) {
+ /* successful write: set cache */
+ ac97->regs[reg] = val;
return;
+ }
}
snd_printd("nm256: ac97 codec not ready..\n");
}
+/*
+ * below copied from OSS driver
+ * this list could perhaps be fused with mixer_regs[] ??
+ *
+ * Initial register values to be written to the AC97 mixer.
+ * While most of these are identical to the reset values, we do this
+ * so that we have most of the register contents cached--this avoids
+ * reading from the mixer directly (which seems to be problematic,
+ * probably due to ignorance).
+ */
+
+struct initialValues
+{
+ unsigned short reg;
+ unsigned short value;
+};
+
+static struct initialValues nm256_ac97_init_val[] =
+{
+ { AC97_MASTER, 0x8000 },
+ { AC97_HEADPHONE, 0x8000 },
+ { AC97_MASTER_MONO, 0x8000 },
+ { AC97_PC_BEEP, 0x8000 },
+ { AC97_PHONE, 0x8008 },
+ { AC97_MIC, 0x8000 },
+ { AC97_LINE, 0x8808 },
+ { AC97_CD, 0x8808 },
+ { AC97_VIDEO, 0x8808 },
+ { AC97_AUX, 0x8808 },
+ { AC97_PCM, 0x8808 },
+ { AC97_REC_SEL, 0x0000 },
+ { AC97_REC_GAIN, 0x0B0B },
+ { AC97_GENERAL_PURPOSE, 0x0000 },
+ { AC97_3D_CONTROL, 0x8000 },
+ { AC97_VENDOR_ID1, 0x8384 },
+ { AC97_VENDOR_ID2, 0x7609 },
+ { 0xffff, 0xffff }
+};
+
+/* static resolution table */
+static struct snd_ac97_res_table nm256_res_table[] = {
+ { AC97_MASTER, 0x1f1f },
+ { AC97_HEADPHONE, 0x1f1f },
+ { AC97_MASTER_MONO, 0x001f },
+ { AC97_PC_BEEP, 0x001f },
+ { AC97_PHONE, 0x001f },
+ { AC97_MIC, 0x001f },
+ { AC97_LINE, 0x1f1f },
+ { AC97_CD, 0x1f1f },
+ { AC97_VIDEO, 0x1f1f },
+ { AC97_AUX, 0x1f1f },
+ { AC97_PCM, 0x1f1f },
+ { AC97_REC_GAIN, 0x0f0f },
+ { } /* terminator */
+};
+
/* initialize the ac97 into a known state */
static void
snd_nm256_ac97_reset(struct snd_ac97 *ac97)
@@ -1213,6 +1272,16 @@
snd_nm256_writeb(chip, 0x6cc, 0x80);
snd_nm256_writeb(chip, 0x6cc, 0x0);
}
+ if (! chip->in_resume) {
+ struct initialValues *x;
+ for (x = nm256_ac97_init_val; x->reg != 0xffff; x++) {
+ /* preload the cache, so as to avoid even a single
+ * read of the mixer regs
+ */
+ set_bit(x->reg, chip->allowed_regs);
+ snd_nm256_ac97_write(ac97, x->reg, x->value);
+ }
+ }
}
/* create an ac97 mixer interface */
@@ -1221,32 +1290,20 @@
{
struct snd_ac97_bus *pbus;
struct snd_ac97_template ac97;
- int i, err;
+ int err;
static struct snd_ac97_bus_ops ops = {
.reset = snd_nm256_ac97_reset,
.write = snd_nm256_ac97_write,
.read = snd_nm256_ac97_read,
};
- /* looks like nm256 hangs up when unexpected registers are touched... */
- static int mixer_regs[] = {
- AC97_MASTER, AC97_HEADPHONE, AC97_MASTER_MONO,
- AC97_PC_BEEP, AC97_PHONE, AC97_MIC, AC97_LINE, AC97_CD,
- AC97_VIDEO, AC97_AUX, AC97_PCM, AC97_REC_SEL,
- AC97_REC_GAIN, AC97_GENERAL_PURPOSE, AC97_3D_CONTROL,
- /*AC97_EXTENDED_ID,*/
- AC97_VENDOR_ID1, AC97_VENDOR_ID2,
- -1
- };
if ((err = snd_ac97_bus(chip->card, 0, &ops, NULL, &pbus)) < 0)
return err;
memset(&ac97, 0, sizeof(ac97));
ac97.scaps = AC97_SCAP_AUDIO; /* we support audio! */
- ac97.limited_regs = 1;
- for (i = 0; mixer_regs[i] >= 0; i++)
- set_bit(mixer_regs[i], ac97.reg_accessed);
ac97.private_data = chip;
+ ac97.res_table = nm256_res_table;
pbus->no_vra = 1;
err = snd_ac97_mixer(pbus, &ac97, &chip->ac97);
if (err < 0)
@@ -1331,6 +1388,7 @@
int i;
/* Perform a full reset on the hardware */
+ chip->in_resume = 1;
pci_restore_state(pci);
pci_enable_device(pci);
snd_nm256_init_chip(chip);
@@ -1348,6 +1406,7 @@
}
snd_power_change_state(card, SNDRV_CTL_POWER_D0);
+ chip->in_resume = 0;
return 0;
}
#endif /* CONFIG_PM */
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: debugging nm256: some results, many questions
2006-03-13 15:50 ` Takashi Iwai
@ 2006-03-14 19:59 ` Florian Schlichting
2006-03-14 20:16 ` Takashi Iwai
0 siblings, 1 reply; 54+ messages in thread
From: Florian Schlichting @ 2006-03-14 19:59 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]
On Mon, Mar 13, 2006 at 04:50:31PM +0100, Takashi Iwai wrote:
> How about the patch below? (It's only for CVS version)
very good. It makes the larger changes that I didn't dare to think of
for lack of insight.
There's just another tiny cosmetical change, to the comments:
--- nm256.c.orig 2006-03-15 00:50:55.000000000 +0800
+++ nm256.c 2006-03-15 00:59:28.000000000 +0800
@@ -1157,7 +1157,8 @@
/*
* some nm256 easily crash when reading from mixer registers
- * thus we're caching both read and written values for reading
+ * thus we're treating it as a write-only mixer and cache the
+ * written values
*/
static unsigned short
snd_nm256_ac97_read(struct snd_ac97 *ac97, unsigned short reg)
@@ -1200,9 +1201,6 @@
}
/*
- * below copied from OSS driver
- * this list could perhaps be fused with mixer_regs[] ??
- *
* Initial register values to be written to the AC97 mixer.
* While most of these are identical to the reset values, we do this
* so that we have most of the register contents cached--this avoids
NB: while trying to compile from CVS with ./cvscompile [...]
-----------
patching file usbaudio.c
Hunk #2 FAILED at 70.
-----------
Running the command again it aparently ignored this problem
Also, there are some warnings during compile and a problem with depmod
loops at install
----------
Building modules, stage 2.
MODPOST
*** Warning: "snd_minor_info_oss_init" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
*** Warning: "snd_lookup_oss_minor_data" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
*** Warning: "snd_info_minor_unregister" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
*** Warning: "snd_minor_info_oss_done" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
*** Warning: "snd_info_minor_register" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
[...]
WARNING: Loop detected:
/lib/modules/2.6.15-max/kernel/sound/acore/snd.ko which needs snd.ko
again!
----------
(and the rest of the ALSA modules is ignored), so although I could
build things, it wouldn't "make install" and I can't make a final smoke
test :-(
Florian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: debugging nm256: some results, many questions
2006-03-14 19:59 ` Florian Schlichting
@ 2006-03-14 20:16 ` Takashi Iwai
2006-03-15 6:09 ` Florian Schlichting
0 siblings, 1 reply; 54+ messages in thread
From: Takashi Iwai @ 2006-03-14 20:16 UTC (permalink / raw)
To: Florian Schlichting; +Cc: alsa-devel
At Wed, 15 Mar 2006 03:59:46 +0800,
Florian Schlichting wrote:
>
> On Mon, Mar 13, 2006 at 04:50:31PM +0100, Takashi Iwai wrote:
> > How about the patch below? (It's only for CVS version)
>
> very good. It makes the larger changes that I didn't dare to think of
> for lack of insight.
>
> There's just another tiny cosmetical change, to the comments:
>
> --- nm256.c.orig 2006-03-15 00:50:55.000000000 +0800
> +++ nm256.c 2006-03-15 00:59:28.000000000 +0800
> @@ -1157,7 +1157,8 @@
>
> /*
> * some nm256 easily crash when reading from mixer registers
> - * thus we're caching both read and written values for reading
> + * thus we're treating it as a write-only mixer and cache the
> + * written values
> */
> static unsigned short
> snd_nm256_ac97_read(struct snd_ac97 *ac97, unsigned short reg)
> @@ -1200,9 +1201,6 @@
> }
>
> /*
> - * below copied from OSS driver
> - * this list could perhaps be fused with mixer_regs[] ??
> - *
> * Initial register values to be written to the AC97 mixer.
> * While most of these are identical to the reset values, we do this
> * so that we have most of the register contents cached--this avoids
Looks fine. I'll fix them.
> NB: while trying to compile from CVS with ./cvscompile [...]
> -----------
> patching file usbaudio.c
> Hunk #2 FAILED at 70.
Oops, forgot to commit. Fixed now.
> -----------
> Running the command again it aparently ignored this problem
>
> Also, there are some warnings during compile and a problem with depmod
> loops at install
> ----------
> Building modules, stage 2.
> MODPOST
> *** Warning: "snd_minor_info_oss_init" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> *** Warning: "snd_lookup_oss_minor_data" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> *** Warning: "snd_info_minor_unregister" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> *** Warning: "snd_minor_info_oss_done" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> *** Warning: "snd_info_minor_register" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
>
> [...]
>
> WARNING: Loop detected:
> /lib/modules/2.6.15-max/kernel/sound/acore/snd.ko which needs snd.ko
> again!
> ----------
> (and the rest of the ALSA modules is ignored), so although I could
> build things, it wouldn't "make install" and I can't make a final smoke
> test :-(
Hm, it sounds like CONFIG_PROC_FS isn't defined properly.
Please check alsa-driver/include/linux/autoconf.h. It's generated by
configure script.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: debugging nm256: some results, many questions
2006-03-14 20:16 ` Takashi Iwai
@ 2006-03-15 6:09 ` Florian Schlichting
2006-03-15 9:55 ` Takashi Iwai
0 siblings, 1 reply; 54+ messages in thread
From: Florian Schlichting @ 2006-03-15 6:09 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
[-- Attachment #1: Type: text/plain, Size: 2510 bytes --]
On Tue, Mar 14, 2006 at 09:16:28PM +0100, Takashi Iwai wrote:
> At Wed, 15 Mar 2006 03:59:46 +0800,
> Florian Schlichting wrote:
> > Also, there are some warnings during compile and a problem with depmod
> > loops at install
> > ----------
> > Building modules, stage 2.
> > MODPOST
> > *** Warning: "snd_minor_info_oss_init" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > *** Warning: "snd_lookup_oss_minor_data" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > *** Warning: "snd_info_minor_unregister" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > *** Warning: "snd_minor_info_oss_done" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > *** Warning: "snd_info_minor_register" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> >
> > [...]
> >
> > WARNING: Loop detected:
> > /lib/modules/2.6.15-max/kernel/sound/acore/snd.ko which needs snd.ko
> > again!
> > ----------
> > (and the rest of the ALSA modules is ignored), so although I could
> > build things, it wouldn't "make install" and I can't make a final smoke
> > test :-(
>
> Hm, it sounds like CONFIG_PROC_FS isn't defined properly.
> Please check alsa-driver/include/linux/autoconf.h. It's generated by
> configure script.
hmmm... do you mean this:
#define CONFIG_ACPI_SLEEP_PROC_FS 1
#undef CONFIG_ACPI_SLEEP_PROC_SLEEP
[...]
#undef CONFIG_PCI_LEGACY_PROC
[...]
#define CONFIG_SCSI_PROC_FS 1
[...]
#define CONFIG_PROC_FS 1
#define CONFIG_PROC_KCORE 1
[...]
#define CONFIG_SND_VERBOSE_PROCFS 1
-.-
I noticed the errors said something with oss. My compile commmand line
was './cvscompile --with-isapnp=no --with-sequencer=no --with-oss=no
--with-cards=nm256' and that still gives the above errors. I just
recompiled with just './cvscompile --with-cards=nm256' and there are no
errors, depmod runs fine, I can insert the module... perfect! The mixer
settings also survive a suspend, apart from Master Volume which becomes
muted (but I guess that's intented? I can't confirm bug#1532)
Thus, are we done fixing an issue that has bugged poor nm256 owners for
years?? bug#328, bug#914 and kbug#3719 look like their
submitters/contributors might be interested in giving it a try...
Summary: treat the nm256 mixer as a write-only device so as to avoid
hangs on initialisation (fixes: bug#....[when confirmed]) and clean up
an older workaround in ac97_codec
Signed-off-by: Florian Schlichting <Florian.Schlichting@gmx.de>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: debugging nm256: some results, many questions
2006-03-15 6:09 ` Florian Schlichting
@ 2006-03-15 9:55 ` Takashi Iwai
2006-03-15 13:23 ` Florian Schlichting
0 siblings, 1 reply; 54+ messages in thread
From: Takashi Iwai @ 2006-03-15 9:55 UTC (permalink / raw)
To: Florian Schlichting; +Cc: alsa-devel
At Wed, 15 Mar 2006 14:09:22 +0800,
Florian Schlichting wrote:
>
> On Tue, Mar 14, 2006 at 09:16:28PM +0100, Takashi Iwai wrote:
> > At Wed, 15 Mar 2006 03:59:46 +0800,
> > Florian Schlichting wrote:
> > > Also, there are some warnings during compile and a problem with depmod
> > > loops at install
> > > ----------
> > > Building modules, stage 2.
> > > MODPOST
> > > *** Warning: "snd_minor_info_oss_init" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > *** Warning: "snd_lookup_oss_minor_data" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > *** Warning: "snd_info_minor_unregister" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > *** Warning: "snd_minor_info_oss_done" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > *** Warning: "snd_info_minor_register" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > >
> > > [...]
> > >
> > > WARNING: Loop detected:
> > > /lib/modules/2.6.15-max/kernel/sound/acore/snd.ko which needs snd.ko
> > > again!
> > > ----------
> > > (and the rest of the ALSA modules is ignored), so although I could
> > > build things, it wouldn't "make install" and I can't make a final smoke
> > > test :-(
> >
> > Hm, it sounds like CONFIG_PROC_FS isn't defined properly.
> > Please check alsa-driver/include/linux/autoconf.h. It's generated by
> > configure script.
>
> hmmm... do you mean this:
>
> #define CONFIG_ACPI_SLEEP_PROC_FS 1
> #undef CONFIG_ACPI_SLEEP_PROC_SLEEP
> [...]
> #undef CONFIG_PCI_LEGACY_PROC
> [...]
> #define CONFIG_SCSI_PROC_FS 1
> [...]
> #define CONFIG_PROC_FS 1
> #define CONFIG_PROC_KCORE 1
> [...]
> #define CONFIG_SND_VERBOSE_PROCFS 1
>
> -.-
>
> I noticed the errors said something with oss. My compile commmand line
> was './cvscompile --with-isapnp=no --with-sequencer=no --with-oss=no
> --with-cards=nm256' and that still gives the above errors. I just
> recompiled with just './cvscompile --with-cards=nm256' and there are no
> errors, depmod runs fine, I can insert the module... perfect!
Then something conflicts. Could you check CONFIG_SND_OSSEMUL in
autoconfig.h?
> The mixer
> settings also survive a suspend, apart from Master Volume which becomes
> muted (but I guess that's intented? I can't confirm bug#1532)
Hm, no, it's not intended. I think this is the side effect of using
ac97->regs[]. The ac97 codec routine mutes the master volume to avoid
noise at suspend, and resumes it with the cache value.
Please try the newer patch below.
> Thus, are we done fixing an issue that has bugged poor nm256 owners for
> years?? bug#328, bug#914 and kbug#3719 look like their
> submitters/contributors might be interested in giving it a try...
>
> Summary: treat the nm256 mixer as a write-only device so as to avoid
> hangs on initialisation (fixes: bug#....[when confirmed]) and clean up
> an older workaround in ac97_codec
> Signed-off-by: Florian Schlichting <Florian.Schlichting@gmx.de>
Thanks, I'll apply the patch once after you confirm the newer one.
Takashi
Index: alsa-kernel/include/ac97_codec.h
===================================================================
RCS file: /home/iwai/cvs/alsa/alsa-kernel/include/ac97_codec.h,v
retrieving revision 1.75
diff -u -r1.75 ac97_codec.h
--- alsa-kernel/include/ac97_codec.h 9 Feb 2006 11:43:01 -0000 1.75
+++ alsa-kernel/include/ac97_codec.h 15 Mar 2006 09:54:37 -0000
@@ -433,6 +433,12 @@
struct snd_info_entry *proc;
};
+/* static resolution table */
+struct snd_ac97_res_table {
+ unsigned short reg; /* register */
+ unsigned short bits; /* resolution bitmask */
+};
+
struct snd_ac97_template {
void *private_data;
void (*private_free) (struct snd_ac97 *ac97);
@@ -440,14 +446,7 @@
unsigned short num; /* number of codec: 0 = primary, 1 = secondary */
unsigned short addr; /* physical address of codec [0-3] */
unsigned int scaps; /* driver capabilities */
- unsigned int limited_regs; /* allow limited registers only */
- DECLARE_BITMAP(reg_accessed, 0x80); /* bit flags */
-};
-
-/* static resolution table */
-struct snd_ac97_res_table {
- unsigned short reg; /* register */
- unsigned short bits; /* resolution bitmask */
+ const struct snd_ac97_res_table *res_table; /* static resolution */
};
struct snd_ac97 {
@@ -476,7 +475,6 @@
unsigned int rates[6]; /* see AC97_RATES_* defines */
unsigned int spdif_status;
unsigned short regs[0x80]; /* register cache */
- unsigned int limited_regs; /* allow limited registers only */
DECLARE_BITMAP(reg_accessed, 0x80); /* bit flags */
union { /* vendor specific code */
struct {
Index: alsa-kernel/pci/ac97/ac97_codec.c
===================================================================
RCS file: /home/iwai/cvs/alsa/alsa-kernel/pci/ac97/ac97_codec.c,v
retrieving revision 1.202
diff -u -r1.202 ac97_codec.c
--- alsa-kernel/pci/ac97/ac97_codec.c 9 Feb 2006 11:46:47 -0000 1.202
+++ alsa-kernel/pci/ac97/ac97_codec.c 15 Mar 2006 09:54:37 -0000
@@ -192,9 +192,6 @@
static int snd_ac97_valid_reg(struct snd_ac97 *ac97, unsigned short reg)
{
- if (ac97->limited_regs && ! test_bit(reg, ac97->reg_accessed))
- return 0;
-
/* filter some registers for buggy codecs */
switch (ac97->id) {
case AC97_ID_AK4540:
@@ -1008,9 +1005,6 @@
break;
}
- if (ac97->limited_regs && test_bit(reg, ac97->reg_accessed))
- return 1; /* allow without check */
-
val = snd_ac97_read(ac97, reg);
if (!(val & mask)) {
/* nothing seems to be here - mute flag is not set */
@@ -1866,8 +1860,7 @@
ac97->num = template->num;
ac97->addr = template->addr;
ac97->scaps = template->scaps;
- ac97->limited_regs = template->limited_regs;
- memcpy(ac97->reg_accessed, template->reg_accessed, sizeof(ac97->reg_accessed));
+ ac97->res_table = template->res_table;
bus->codec[ac97->num] = ac97;
mutex_init(&ac97->reg_mutex);
mutex_init(&ac97->page_mutex);
Index: alsa-kernel/pci/nm256/nm256.c
===================================================================
RCS file: /home/iwai/cvs/alsa/alsa-kernel/pci/nm256/nm256.c,v
retrieving revision 1.81
diff -u -r1.81 nm256.c
--- alsa-kernel/pci/nm256/nm256.c 16 Jan 2006 16:40:06 -0000 1.81
+++ alsa-kernel/pci/nm256/nm256.c 15 Mar 2006 09:54:37 -0000
@@ -228,6 +228,7 @@
unsigned int use_cache: 1; /* use one big coef. table */
unsigned int reset_workaround: 1; /* Workaround for some laptops to avoid freeze */
unsigned int reset_workaround_2: 1; /* Extended workaround for some other laptops to avoid freeze */
+ unsigned int in_resume: 1;
int mixer_base; /* register offset of ac97 mixer */
int mixer_status_offset; /* offset of mixer status reg. */
@@ -242,6 +243,7 @@
struct nm256_stream streams[2];
struct snd_ac97 *ac97;
+ unsigned short *ac97_regs; /* register caches, only for valid regs */
struct snd_pcm *pcm;
@@ -1153,23 +1155,63 @@
return 0;
}
+/*
+ * Initial register values to be written to the AC97 mixer.
+ * While most of these are identical to the reset values, we do this
+ * so that we have most of the register contents cached--this avoids
+ * reading from the mixer directly (which seems to be problematic,
+ * probably due to ignorance).
+ */
+
+struct initialValues {
+ unsigned short reg;
+ unsigned short value;
+};
+
+static struct initialValues nm256_ac97_init_val[] =
+{
+ { AC97_MASTER, 0x8000 },
+ { AC97_HEADPHONE, 0x8000 },
+ { AC97_MASTER_MONO, 0x8000 },
+ { AC97_PC_BEEP, 0x8000 },
+ { AC97_PHONE, 0x8008 },
+ { AC97_MIC, 0x8000 },
+ { AC97_LINE, 0x8808 },
+ { AC97_CD, 0x8808 },
+ { AC97_VIDEO, 0x8808 },
+ { AC97_AUX, 0x8808 },
+ { AC97_PCM, 0x8808 },
+ { AC97_REC_SEL, 0x0000 },
+ { AC97_REC_GAIN, 0x0B0B },
+ { AC97_GENERAL_PURPOSE, 0x0000 },
+ { AC97_3D_CONTROL, 0x8000 },
+ { AC97_VENDOR_ID1, 0x8384 },
+ { AC97_VENDOR_ID2, 0x7609 },
+};
+
+static int nm256_ac97_idx(unsigned short reg)
+{
+ int i;
+ for (i = 0; i < ARRAY_SIZE(nm256_ac97_init_val); i++)
+ if (nm256_ac97_init_val[i].reg == reg)
+ return i;
+ return -1;
+}
+
/*
+ * some nm256 easily crash when reading from mixer registers
+ * thus we're treating it as a write-only mixer and cache the
+ * written values
*/
static unsigned short
snd_nm256_ac97_read(struct snd_ac97 *ac97, unsigned short reg)
{
struct nm256 *chip = ac97->private_data;
- int res;
-
- if (reg >= 128)
- return 0;
+ int idx = nm256_ac97_idx(reg);
- if (! snd_nm256_ac97_ready(chip))
+ if (idx < 0)
return 0;
- res = snd_nm256_readw(chip, chip->mixer_base + reg);
- /* Magic delay. Bleah yucky. */
- msleep(1);
- return res;
+ return chip->ac97_regs[idx];
}
/*
@@ -1180,8 +1222,12 @@
{
struct nm256 *chip = ac97->private_data;
int tries = 2;
+ int idx = nm256_ac97_idx(reg);
u32 base;
+ if (idx < 0)
+ return;
+
base = chip->mixer_base;
snd_nm256_ac97_ready(chip);
@@ -1190,12 +1236,32 @@
while (tries-- > 0) {
snd_nm256_writew(chip, base + reg, val);
msleep(1); /* a little delay here seems better.. */
- if (snd_nm256_ac97_ready(chip))
+ if (snd_nm256_ac97_ready(chip)) {
+ /* successful write: set cache */
+ chip->ac97_regs[idx] = val;
return;
+ }
}
snd_printd("nm256: ac97 codec not ready..\n");
}
+/* static resolution table */
+static struct snd_ac97_res_table nm256_res_table[] = {
+ { AC97_MASTER, 0x1f1f },
+ { AC97_HEADPHONE, 0x1f1f },
+ { AC97_MASTER_MONO, 0x001f },
+ { AC97_PC_BEEP, 0x001f },
+ { AC97_PHONE, 0x001f },
+ { AC97_MIC, 0x001f },
+ { AC97_LINE, 0x1f1f },
+ { AC97_CD, 0x1f1f },
+ { AC97_VIDEO, 0x1f1f },
+ { AC97_AUX, 0x1f1f },
+ { AC97_PCM, 0x1f1f },
+ { AC97_REC_GAIN, 0x0f0f },
+ { } /* terminator */
+};
+
/* initialize the ac97 into a known state */
static void
snd_nm256_ac97_reset(struct snd_ac97 *ac97)
@@ -1213,6 +1279,16 @@
snd_nm256_writeb(chip, 0x6cc, 0x80);
snd_nm256_writeb(chip, 0x6cc, 0x0);
}
+ if (! chip->in_resume) {
+ int i;
+ for (i = 0; i < ARRAY_SIZE(nm256_ac97_init_val); i++) {
+ /* preload the cache, so as to avoid even a single
+ * read of the mixer regs
+ */
+ snd_nm256_ac97_write(ac97, nm256_ac97_init_val[i].reg,
+ nm256_ac97_init_val[i].value);
+ }
+ }
}
/* create an ac97 mixer interface */
@@ -1221,32 +1297,25 @@
{
struct snd_ac97_bus *pbus;
struct snd_ac97_template ac97;
- int i, err;
+ int err;
static struct snd_ac97_bus_ops ops = {
.reset = snd_nm256_ac97_reset,
.write = snd_nm256_ac97_write,
.read = snd_nm256_ac97_read,
};
- /* looks like nm256 hangs up when unexpected registers are touched... */
- static int mixer_regs[] = {
- AC97_MASTER, AC97_HEADPHONE, AC97_MASTER_MONO,
- AC97_PC_BEEP, AC97_PHONE, AC97_MIC, AC97_LINE, AC97_CD,
- AC97_VIDEO, AC97_AUX, AC97_PCM, AC97_REC_SEL,
- AC97_REC_GAIN, AC97_GENERAL_PURPOSE, AC97_3D_CONTROL,
- /*AC97_EXTENDED_ID,*/
- AC97_VENDOR_ID1, AC97_VENDOR_ID2,
- -1
- };
+
+ chip->ac97_regs = kcalloc(sizeof(short),
+ ARRAY_SIZE(nm256_ac97_init_val), GFP_KERNEL);
+ if (! chip->ac97_regs)
+ return -ENOMEM;
if ((err = snd_ac97_bus(chip->card, 0, &ops, NULL, &pbus)) < 0)
return err;
memset(&ac97, 0, sizeof(ac97));
ac97.scaps = AC97_SCAP_AUDIO; /* we support audio! */
- ac97.limited_regs = 1;
- for (i = 0; mixer_regs[i] >= 0; i++)
- set_bit(mixer_regs[i], ac97.reg_accessed);
ac97.private_data = chip;
+ ac97.res_table = nm256_res_table;
pbus->no_vra = 1;
err = snd_ac97_mixer(pbus, &ac97, &chip->ac97);
if (err < 0)
@@ -1331,6 +1400,7 @@
int i;
/* Perform a full reset on the hardware */
+ chip->in_resume = 1;
pci_restore_state(pci);
pci_enable_device(pci);
snd_nm256_init_chip(chip);
@@ -1348,6 +1418,7 @@
}
snd_power_change_state(card, SNDRV_CTL_POWER_D0);
+ chip->in_resume = 0;
return 0;
}
#endif /* CONFIG_PM */
@@ -1372,6 +1443,7 @@
free_irq(chip->irq, chip);
pci_disable_device(chip->pci);
+ kfree(chip->ac97_regs);
kfree(chip);
return 0;
}
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply [flat|nested] 54+ messages in thread* Re: debugging nm256: some results, many questions
2006-03-15 9:55 ` Takashi Iwai
@ 2006-03-15 13:23 ` Florian Schlichting
2006-03-15 15:42 ` Takashi Iwai
0 siblings, 1 reply; 54+ messages in thread
From: Florian Schlichting @ 2006-03-15 13:23 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
[-- Attachment #1.1: Type: text/plain, Size: 3341 bytes --]
On Wed, Mar 15, 2006 at 10:55:36AM +0100, Takashi Iwai wrote:
> At Wed, 15 Mar 2006 14:09:22 +0800,
> Florian Schlichting wrote:
> >
> > On Tue, Mar 14, 2006 at 09:16:28PM +0100, Takashi Iwai wrote:
> > > At Wed, 15 Mar 2006 03:59:46 +0800,
> > > Florian Schlichting wrote:
> > > > Also, there are some warnings during compile and a problem with depmod
> > > > loops at install
> > > > ----------
> > > > Building modules, stage 2.
> > > > MODPOST
> > > > *** Warning: "snd_minor_info_oss_init" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > > *** Warning: "snd_lookup_oss_minor_data" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > > *** Warning: "snd_info_minor_unregister" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > > *** Warning: "snd_minor_info_oss_done" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > > *** Warning: "snd_info_minor_register" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > >
> > > > [...]
> > > >
> > > > WARNING: Loop detected:
> > > > /lib/modules/2.6.15-max/kernel/sound/acore/snd.ko which needs snd.ko
> > > > again!
> > > > ----------
> > > > (and the rest of the ALSA modules is ignored), so although I could
> > > > build things, it wouldn't "make install" and I can't make a final smoke
> > > > test :-(
> > >
> > > Hm, it sounds like CONFIG_PROC_FS isn't defined properly.
> > > Please check alsa-driver/include/linux/autoconf.h. It's generated by
> > > configure script.
> >
> > hmmm... do you mean this:
> >
> > #define CONFIG_ACPI_SLEEP_PROC_FS 1
> > #undef CONFIG_ACPI_SLEEP_PROC_SLEEP
> > [...]
> > #undef CONFIG_PCI_LEGACY_PROC
> > [...]
> > #define CONFIG_SCSI_PROC_FS 1
> > [...]
> > #define CONFIG_PROC_FS 1
> > #define CONFIG_PROC_KCORE 1
> > [...]
> > #define CONFIG_SND_VERBOSE_PROCFS 1
> >
> > -.-
> >
> > I noticed the errors said something with oss. My compile commmand line
> > was './cvscompile --with-isapnp=no --with-sequencer=no --with-oss=no
> > --with-cards=nm256' and that still gives the above errors. I just
> > recompiled with just './cvscompile --with-cards=nm256' and there are no
> > errors, depmod runs fine, I can insert the module... perfect!
>
> Then something conflicts. Could you check CONFIG_SND_OSSEMUL in
> autoconfig.h?
I did a few tests with different options, and it's clearly the
--with-oss=no that causes the errors during compile and install
#define CONFIG_SND_OSSEMUL 1 - with the working options,
/* #undef CONFIG_SND_OSSEMUL */ when the errors occur - but it's in there
twice, at line 1276 and 1300, in sections "include/autoconf-extra.h." and
"include/config1.h"!
I'm attaching the whole file for a ./cvscompile --with-cards=nm256
--with-oss=no
>
> > The mixer
> > settings also survive a suspend, apart from Master Volume which becomes
> > muted (but I guess that's intented? I can't confirm bug#1532)
>
> Hm, no, it's not intended. I think this is the side effect of using
> ac97->regs[]. The ac97 codec routine mutes the master volume to avoid
> noise at suspend, and resumes it with the cache value.
>
> Please try the newer patch below.
I've tried it, it works well and all the registers including Master
Volume are restored to their pre-suspend values.
Florian
[-- Attachment #1.2: autoconf.h --]
[-- Type: text/x-chdr, Size: 33597 bytes --]
/*
* Automatically generated C config: don't edit
* Linux kernel version: 2.6.15-max
* Mon Mar 13 12:41:33 2006
*/
#define AUTOCONF_INCLUDED
#define CONFIG_X86_32 1
#define CONFIG_SEMAPHORE_SLEEPERS 1
#define CONFIG_X86 1
#define CONFIG_MMU 1
#define CONFIG_UID16 1
#define CONFIG_GENERIC_ISA_DMA 1
#define CONFIG_GENERIC_IOMAP 1
#define CONFIG_ARCH_MAY_HAVE_PC_FDC 1
/*
* Code maturity level options
*/
#define CONFIG_EXPERIMENTAL 1
#define CONFIG_CLEAN_COMPILE 1
#define CONFIG_BROKEN_ON_SMP 1
#define CONFIG_LOCK_KERNEL 1
#define CONFIG_INIT_ENV_ARG_LIMIT 32
/*
* General setup
*/
#define CONFIG_LOCALVERSION ""
#define CONFIG_LOCALVERSION_AUTO 1
#define CONFIG_SWAP 1
#define CONFIG_SYSVIPC 1
#undef CONFIG_POSIX_MQUEUE
#define CONFIG_BSD_PROCESS_ACCT 1
#undef CONFIG_BSD_PROCESS_ACCT_V3
#define CONFIG_SYSCTL 1
#undef CONFIG_AUDIT
#define CONFIG_HOTPLUG 1
#define CONFIG_KOBJECT_UEVENT 1
#undef CONFIG_IKCONFIG
#define CONFIG_INITRAMFS_SOURCE ""
#undef CONFIG_CC_OPTIMIZE_FOR_SIZE
#undef CONFIG_EMBEDDED
#define CONFIG_KALLSYMS 1
#undef CONFIG_KALLSYMS_EXTRA_PASS
#define CONFIG_PRINTK 1
#define CONFIG_BUG 1
#define CONFIG_BASE_FULL 1
#define CONFIG_FUTEX 1
#define CONFIG_EPOLL 1
#define CONFIG_SHMEM 1
#define CONFIG_CC_ALIGN_FUNCTIONS 0
#define CONFIG_CC_ALIGN_LABELS 0
#define CONFIG_CC_ALIGN_LOOPS 0
#define CONFIG_CC_ALIGN_JUMPS 0
#undef CONFIG_TINY_SHMEM
#define CONFIG_BASE_SMALL 0
/*
* Loadable module support
*/
#define CONFIG_MODULES 1
#define CONFIG_MODULE_UNLOAD 1
#undef CONFIG_MODULE_FORCE_UNLOAD
#define CONFIG_OBSOLETE_MODPARM 1
#undef CONFIG_MODVERSIONS
#undef CONFIG_MODULE_SRCVERSION_ALL
#define CONFIG_KMOD 1
/*
* Block layer
*/
#undef CONFIG_LBD
/*
* IO Schedulers
*/
#define CONFIG_IOSCHED_NOOP 1
#define CONFIG_IOSCHED_AS 1
#define CONFIG_IOSCHED_DEADLINE 1
#define CONFIG_IOSCHED_CFQ 1
#define CONFIG_DEFAULT_AS 1
#undef CONFIG_DEFAULT_DEADLINE
#undef CONFIG_DEFAULT_CFQ
#undef CONFIG_DEFAULT_NOOP
#define CONFIG_DEFAULT_IOSCHED "anticipatory"
/*
* Processor type and features
*/
#define CONFIG_X86_PC 1
#undef CONFIG_X86_ELAN
#undef CONFIG_X86_VOYAGER
#undef CONFIG_X86_NUMAQ
#undef CONFIG_X86_SUMMIT
#undef CONFIG_X86_BIGSMP
#undef CONFIG_X86_VISWS
#undef CONFIG_X86_GENERICARCH
#undef CONFIG_X86_ES7000
#undef CONFIG_M386
#undef CONFIG_M486
#undef CONFIG_M586
#undef CONFIG_M586TSC
#undef CONFIG_M586MMX
#undef CONFIG_M686
#undef CONFIG_MPENTIUMII
#define CONFIG_MPENTIUMIII 1
#undef CONFIG_MPENTIUMM
#undef CONFIG_MPENTIUM4
#undef CONFIG_MK6
#undef CONFIG_MK7
#undef CONFIG_MK8
#undef CONFIG_MCRUSOE
#undef CONFIG_MEFFICEON
#undef CONFIG_MWINCHIPC6
#undef CONFIG_MWINCHIP2
#undef CONFIG_MWINCHIP3D
#undef CONFIG_MGEODEGX1
#undef CONFIG_MCYRIXIII
#undef CONFIG_MVIAC3_2
#undef CONFIG_X86_GENERIC
#define CONFIG_X86_CMPXCHG 1
#define CONFIG_X86_XADD 1
#define CONFIG_X86_L1_CACHE_SHIFT 5
#define CONFIG_RWSEM_XCHGADD_ALGORITHM 1
#define CONFIG_GENERIC_CALIBRATE_DELAY 1
#define CONFIG_X86_WP_WORKS_OK 1
#define CONFIG_X86_INVLPG 1
#define CONFIG_X86_BSWAP 1
#define CONFIG_X86_POPAD_OK 1
#define CONFIG_X86_CMPXCHG64 1
#define CONFIG_X86_GOOD_APIC 1
#define CONFIG_X86_INTEL_USERCOPY 1
#define CONFIG_X86_USE_PPRO_CHECKSUM 1
#define CONFIG_X86_TSC 1
#define CONFIG_HPET_TIMER 1
#define CONFIG_HPET_EMULATE_RTC 1
#undef CONFIG_SMP
#undef CONFIG_PREEMPT_NONE
#undef CONFIG_PREEMPT_VOLUNTARY
#define CONFIG_PREEMPT 1
#define CONFIG_PREEMPT_BKL 1
#undef CONFIG_X86_UP_APIC
#define CONFIG_X86_MCE 1
#undef CONFIG_X86_MCE_NONFATAL
#undef CONFIG_TOSHIBA
#undef CONFIG_I8K
#undef CONFIG_X86_REBOOTFIXUPS
#undef CONFIG_MICROCODE
#undef CONFIG_X86_MSR
#undef CONFIG_X86_CPUID
/*
* Firmware Drivers
*/
#undef CONFIG_EDD
#undef CONFIG_DELL_RBU
#undef CONFIG_DCDBAS
#define CONFIG_NOHIGHMEM 1
#undef CONFIG_HIGHMEM4G
#undef CONFIG_HIGHMEM64G
#define CONFIG_SELECT_MEMORY_MODEL 1
#define CONFIG_FLATMEM_MANUAL 1
#undef CONFIG_DISCONTIGMEM_MANUAL
#undef CONFIG_SPARSEMEM_MANUAL
#define CONFIG_FLATMEM 1
#define CONFIG_FLAT_NODE_MEM_MAP 1
#undef CONFIG_SPARSEMEM_STATIC
#define CONFIG_SPLIT_PTLOCK_CPUS 4
#undef CONFIG_MATH_EMULATION
#define CONFIG_MTRR 1
#undef CONFIG_EFI
#undef CONFIG_REGPARM
#define CONFIG_SECCOMP 1
#undef CONFIG_HZ_100
#define CONFIG_HZ_250 1
#undef CONFIG_HZ_1000
#define CONFIG_HZ 250
#define CONFIG_PHYSICAL_START 0x100000
#undef CONFIG_KEXEC
/*
* Power management options (ACPI, APM)
*/
#define CONFIG_PM 1
#undef CONFIG_PM_LEGACY
#undef CONFIG_PM_DEBUG
#define CONFIG_SOFTWARE_SUSPEND 1
#define CONFIG_PM_STD_PARTITION "/dev/hda2"
/*
* ACPI (Advanced Configuration and Power Interface) Support
*/
#define CONFIG_ACPI 1
#define CONFIG_ACPI_SLEEP 1
#define CONFIG_ACPI_SLEEP_PROC_FS 1
#undef CONFIG_ACPI_SLEEP_PROC_SLEEP
#define CONFIG_ACPI_AC 1
#define CONFIG_ACPI_BATTERY 1
#define CONFIG_ACPI_BUTTON 1
#define CONFIG_ACPI_VIDEO 1
#undef CONFIG_ACPI_HOTKEY
#define CONFIG_ACPI_FAN 1
#define CONFIG_ACPI_PROCESSOR 1
#define CONFIG_ACPI_THERMAL 1
#undef CONFIG_ACPI_ASUS
#undef CONFIG_ACPI_IBM
#undef CONFIG_ACPI_TOSHIBA
#define CONFIG_ACPI_BLACKLIST_YEAR 0
#undef CONFIG_ACPI_DEBUG
#define CONFIG_ACPI_EC 1
#define CONFIG_ACPI_POWER 1
#define CONFIG_ACPI_SYSTEM 1
#define CONFIG_X86_PM_TIMER 1
#undef CONFIG_ACPI_CONTAINER
/*
* APM (Advanced Power Management) BIOS Support
*/
/*
* CPU Frequency scaling
*/
#undef CONFIG_CPU_FREQ
/*
* Bus options (PCI, PCMCIA, EISA, MCA, ISA)
*/
#define CONFIG_PCI 1
#undef CONFIG_PCI_GOBIOS
#undef CONFIG_PCI_GOMMCONFIG
#undef CONFIG_PCI_GODIRECT
#define CONFIG_PCI_GOANY 1
#define CONFIG_PCI_BIOS 1
#define CONFIG_PCI_DIRECT 1
#define CONFIG_PCI_MMCONFIG 1
#undef CONFIG_PCIEPORTBUS
#undef CONFIG_PCI_LEGACY_PROC
#define CONFIG_ISA_DMA_API 1
#undef CONFIG_ISA
#undef CONFIG_MCA
#undef CONFIG_SCx200
/*
* PCCARD (PCMCIA/CardBus) support
*/
#define CONFIG_PCCARD_MODULE 1
#undef CONFIG_PCMCIA_DEBUG
#define CONFIG_PCMCIA_MODULE 1
#define CONFIG_PCMCIA_LOAD_CIS 1
#define CONFIG_PCMCIA_IOCTL 1
#define CONFIG_CARDBUS 1
/*
* PC-card bridges
*/
#define CONFIG_YENTA_MODULE 1
#undef CONFIG_PD6729
#undef CONFIG_I82092
#define CONFIG_PCCARD_NONSTATIC_MODULE 1
/*
* PCI Hotplug Support
*/
#define CONFIG_HOTPLUG_PCI_MODULE 1
#undef CONFIG_HOTPLUG_PCI_FAKE
#undef CONFIG_HOTPLUG_PCI_COMPAQ
#undef CONFIG_HOTPLUG_PCI_ACPI
#undef CONFIG_HOTPLUG_PCI_CPCI
#define CONFIG_HOTPLUG_PCI_SHPC_MODULE 1
#undef CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE
/*
* Executable file formats
*/
#define CONFIG_BINFMT_ELF 1
#undef CONFIG_BINFMT_AOUT
#undef CONFIG_BINFMT_MISC
/*
* Networking
*/
#define CONFIG_NET 1
/*
* Networking options
*/
#define CONFIG_PACKET 1
#define CONFIG_PACKET_MMAP 1
#define CONFIG_UNIX 1
#undef CONFIG_NET_KEY
#define CONFIG_INET 1
#undef CONFIG_IP_MULTICAST
#undef CONFIG_IP_ADVANCED_ROUTER
#define CONFIG_IP_FIB_HASH 1
#undef CONFIG_IP_PNP
#undef CONFIG_NET_IPIP
#undef CONFIG_NET_IPGRE
#undef CONFIG_ARPD
#undef CONFIG_SYN_COOKIES
#undef CONFIG_INET_AH
#undef CONFIG_INET_ESP
#undef CONFIG_INET_IPCOMP
#undef CONFIG_INET_TUNNEL
#define CONFIG_INET_DIAG 1
#define CONFIG_INET_TCP_DIAG 1
#undef CONFIG_TCP_CONG_ADVANCED
#define CONFIG_TCP_CONG_BIC 1
#undef CONFIG_IPV6
#undef CONFIG_NETFILTER
/*
* DCCP Configuration (EXPERIMENTAL)
*/
#undef CONFIG_IP_DCCP
/*
* SCTP Configuration (EXPERIMENTAL)
*/
#undef CONFIG_IP_SCTP
#undef CONFIG_ATM
#undef CONFIG_BRIDGE
#undef CONFIG_VLAN_8021Q
#undef CONFIG_DECNET
#undef CONFIG_LLC2
#undef CONFIG_IPX
#undef CONFIG_ATALK
#undef CONFIG_X25
#undef CONFIG_LAPB
#undef CONFIG_NET_DIVERT
#undef CONFIG_ECONET
#undef CONFIG_WAN_ROUTER
/*
* QoS and/or fair queueing
*/
#undef CONFIG_NET_SCHED
/*
* Network testing
*/
#undef CONFIG_NET_PKTGEN
#undef CONFIG_HAMRADIO
#undef CONFIG_IRDA
#undef CONFIG_BT
#undef CONFIG_IEEE80211
/*
* Device Drivers
*/
/*
* Generic Driver Options
*/
#define CONFIG_STANDALONE 1
#define CONFIG_PREVENT_FIRMWARE_BUILD 1
#define CONFIG_FW_LOADER_MODULE 1
/*
* Connector - unified userspace <-> kernelspace linker
*/
#undef CONFIG_CONNECTOR
/*
* Memory Technology Devices (MTD)
*/
#undef CONFIG_MTD
/*
* Parallel port support
*/
#undef CONFIG_PARPORT
/*
* Plug and Play support
*/
#undef CONFIG_PNP
/*
* Block devices
*/
#define CONFIG_BLK_DEV_FD_MODULE 1
#undef CONFIG_BLK_CPQ_DA
#undef CONFIG_BLK_CPQ_CISS_DA
#undef CONFIG_BLK_DEV_DAC960
#undef CONFIG_BLK_DEV_UMEM
#undef CONFIG_BLK_DEV_COW_COMMON
#undef CONFIG_BLK_DEV_LOOP
#undef CONFIG_BLK_DEV_NBD
#undef CONFIG_BLK_DEV_SX8
#undef CONFIG_BLK_DEV_UB
#undef CONFIG_BLK_DEV_RAM
#define CONFIG_BLK_DEV_RAM_COUNT 16
#undef CONFIG_CDROM_PKTCDVD
#undef CONFIG_ATA_OVER_ETH
/*
* ATA/ATAPI/MFM/RLL support
*/
#define CONFIG_IDE 1
#define CONFIG_BLK_DEV_IDE 1
/*
* Please see Documentation/ide.txt for help/info on IDE drives
*/
#undef CONFIG_BLK_DEV_IDE_SATA
#undef CONFIG_BLK_DEV_HD_IDE
#define CONFIG_BLK_DEV_IDEDISK 1
#undef CONFIG_IDEDISK_MULTI_MODE
#undef CONFIG_BLK_DEV_IDECS
#undef CONFIG_BLK_DEV_IDECD
#undef CONFIG_BLK_DEV_IDETAPE
#undef CONFIG_BLK_DEV_IDEFLOPPY
#undef CONFIG_BLK_DEV_IDESCSI
#undef CONFIG_IDE_TASK_IOCTL
/*
* IDE chipset support/bugfixes
*/
#define CONFIG_IDE_GENERIC 1
#undef CONFIG_BLK_DEV_CMD640
#define CONFIG_BLK_DEV_IDEPCI 1
#undef CONFIG_IDEPCI_SHARE_IRQ
#undef CONFIG_BLK_DEV_OFFBOARD
#undef CONFIG_BLK_DEV_GENERIC
#undef CONFIG_BLK_DEV_OPTI621
#undef CONFIG_BLK_DEV_RZ1000
#define CONFIG_BLK_DEV_IDEDMA_PCI 1
#undef CONFIG_BLK_DEV_IDEDMA_FORCED
#define CONFIG_IDEDMA_PCI_AUTO 1
#undef CONFIG_IDEDMA_ONLYDISK
#undef CONFIG_BLK_DEV_AEC62XX
#undef CONFIG_BLK_DEV_ALI15X3
#undef CONFIG_BLK_DEV_AMD74XX
#undef CONFIG_BLK_DEV_ATIIXP
#undef CONFIG_BLK_DEV_CMD64X
#undef CONFIG_BLK_DEV_TRIFLEX
#undef CONFIG_BLK_DEV_CY82C693
#undef CONFIG_BLK_DEV_CS5520
#undef CONFIG_BLK_DEV_CS5530
#undef CONFIG_BLK_DEV_CS5535
#undef CONFIG_BLK_DEV_HPT34X
#undef CONFIG_BLK_DEV_HPT366
#undef CONFIG_BLK_DEV_SC1200
#undef CONFIG_BLK_DEV_PIIX
#undef CONFIG_BLK_DEV_IT821X
#undef CONFIG_BLK_DEV_NS87415
#undef CONFIG_BLK_DEV_PDC202XX_OLD
#undef CONFIG_BLK_DEV_PDC202XX_NEW
#undef CONFIG_BLK_DEV_SVWKS
#undef CONFIG_BLK_DEV_SIIMAGE
#undef CONFIG_BLK_DEV_SIS5513
#undef CONFIG_BLK_DEV_SLC90E66
#undef CONFIG_BLK_DEV_TRM290
#undef CONFIG_BLK_DEV_VIA82CXXX
#undef CONFIG_IDE_ARM
#define CONFIG_BLK_DEV_IDEDMA 1
#undef CONFIG_IDEDMA_IVB
#define CONFIG_IDEDMA_AUTO 1
#undef CONFIG_BLK_DEV_HD
/*
* SCSI device support
*/
#undef CONFIG_RAID_ATTRS
#define CONFIG_SCSI_MODULE 1
#define CONFIG_SCSI_PROC_FS 1
/*
* SCSI support type (disk, tape, CD-ROM)
*/
#define CONFIG_BLK_DEV_SD_MODULE 1
#undef CONFIG_CHR_DEV_ST
#undef CONFIG_CHR_DEV_OSST
#undef CONFIG_BLK_DEV_SR
#undef CONFIG_CHR_DEV_SG
#undef CONFIG_CHR_DEV_SCH
/*
* Some SCSI devices (e.g. CD jukebox) support multiple LUNs
*/
#undef CONFIG_SCSI_MULTI_LUN
#undef CONFIG_SCSI_CONSTANTS
#undef CONFIG_SCSI_LOGGING
/*
* SCSI Transport Attributes
*/
#undef CONFIG_SCSI_SPI_ATTRS
#undef CONFIG_SCSI_FC_ATTRS
#undef CONFIG_SCSI_ISCSI_ATTRS
#undef CONFIG_SCSI_SAS_ATTRS
/*
* SCSI low-level drivers
*/
#undef CONFIG_ISCSI_TCP
#undef CONFIG_BLK_DEV_3W_XXXX_RAID
#undef CONFIG_SCSI_3W_9XXX
#undef CONFIG_SCSI_ACARD
#undef CONFIG_SCSI_AACRAID
#undef CONFIG_SCSI_AIC7XXX
#undef CONFIG_SCSI_AIC7XXX_OLD
#undef CONFIG_SCSI_AIC79XX
#undef CONFIG_SCSI_DPT_I2O
#undef CONFIG_MEGARAID_MM
#undef CONFIG_MEGARAID_LEGACY
#undef CONFIG_MEGARAID_SAS
#undef CONFIG_SCSI_SATA
#undef CONFIG_SCSI_BUSLOGIC
#undef CONFIG_SCSI_DMX3191D
#undef CONFIG_SCSI_EATA
#undef CONFIG_SCSI_FUTURE_DOMAIN
#undef CONFIG_SCSI_GDTH
#undef CONFIG_SCSI_IPS
#undef CONFIG_SCSI_INITIO
#undef CONFIG_SCSI_INIA100
#undef CONFIG_SCSI_SYM53C8XX_2
#undef CONFIG_SCSI_IPR
#undef CONFIG_SCSI_QLOGIC_FC
#undef CONFIG_SCSI_QLOGIC_1280
#define CONFIG_SCSI_QLA2XXX_MODULE 1
#undef CONFIG_SCSI_QLA21XX
#undef CONFIG_SCSI_QLA22XX
#undef CONFIG_SCSI_QLA2300
#undef CONFIG_SCSI_QLA2322
#undef CONFIG_SCSI_QLA6312
#undef CONFIG_SCSI_QLA24XX
#undef CONFIG_SCSI_LPFC
#undef CONFIG_SCSI_DC395x
#undef CONFIG_SCSI_DC390T
#undef CONFIG_SCSI_NSP32
#undef CONFIG_SCSI_DEBUG
/*
* PCMCIA SCSI adapter support
*/
#undef CONFIG_PCMCIA_AHA152X
#undef CONFIG_PCMCIA_FDOMAIN
#undef CONFIG_PCMCIA_NINJA_SCSI
#undef CONFIG_PCMCIA_QLOGIC
#undef CONFIG_PCMCIA_SYM53C500
/*
* Multi-device support (RAID and LVM)
*/
#undef CONFIG_MD
/*
* Fusion MPT device support
*/
#undef CONFIG_FUSION
#undef CONFIG_FUSION_SPI
#undef CONFIG_FUSION_FC
#undef CONFIG_FUSION_SAS
/*
* IEEE 1394 (FireWire) support
*/
#undef CONFIG_IEEE1394
/*
* I2O device support
*/
#undef CONFIG_I2O
/*
* Network device support
*/
#define CONFIG_NETDEVICES 1
#undef CONFIG_DUMMY
#undef CONFIG_BONDING
#undef CONFIG_EQUALIZER
#undef CONFIG_TUN
/*
* ARCnet devices
*/
#undef CONFIG_ARCNET
/*
* PHY device support
*/
#undef CONFIG_PHYLIB
/*
* Ethernet (10 or 100Mbit)
*/
#define CONFIG_NET_ETHERNET 1
#define CONFIG_MII 1
#undef CONFIG_HAPPYMEAL
#undef CONFIG_SUNGEM
#undef CONFIG_CASSINI
#define CONFIG_NET_VENDOR_3COM 1
#define CONFIG_VORTEX 1
#undef CONFIG_TYPHOON
/*
* Tulip family network device support
*/
#undef CONFIG_NET_TULIP
#undef CONFIG_HP100
#undef CONFIG_NET_PCI
/*
* Ethernet (1000 Mbit)
*/
#undef CONFIG_DL2K
#undef CONFIG_E1000
#undef CONFIG_NS83820
#undef CONFIG_HAMACHI
#undef CONFIG_YELLOWFIN
#undef CONFIG_R8169
#undef CONFIG_SIS190
#undef CONFIG_SKGE
#undef CONFIG_SK98LIN
#undef CONFIG_TIGON3
#undef CONFIG_BNX2
/*
* Ethernet (10000 Mbit)
*/
#undef CONFIG_CHELSIO_T1
#undef CONFIG_IXGB
#undef CONFIG_S2IO
/*
* Token Ring devices
*/
#undef CONFIG_TR
/*
* Wireless LAN (non-hamradio)
*/
#define CONFIG_NET_RADIO 1
/*
* Obsolete Wireless cards support (pre-802.11)
*/
#undef CONFIG_STRIP
#undef CONFIG_PCMCIA_WAVELAN
#undef CONFIG_PCMCIA_NETWAVE
/*
* Wireless 802.11 Frequency Hopping cards support
*/
#undef CONFIG_PCMCIA_RAYCS
/*
* Wireless 802.11b ISA/PCI cards support
*/
#undef CONFIG_AIRO
#undef CONFIG_HERMES
#undef CONFIG_ATMEL
/*
* Wireless 802.11b Pcmcia/Cardbus cards support
*/
#undef CONFIG_AIRO_CS
#undef CONFIG_PCMCIA_WL3501
/*
* Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support
*/
#undef CONFIG_PRISM54
#undef CONFIG_HOSTAP
#define CONFIG_NET_WIRELESS 1
/*
* PCMCIA network device support
*/
#undef CONFIG_NET_PCMCIA
/*
* Wan interfaces
*/
#undef CONFIG_WAN
#undef CONFIG_FDDI
#undef CONFIG_HIPPI
#undef CONFIG_PPP
#undef CONFIG_SLIP
#undef CONFIG_NET_FC
#undef CONFIG_SHAPER
#undef CONFIG_NETCONSOLE
#undef CONFIG_NETPOLL
#undef CONFIG_NET_POLL_CONTROLLER
/*
* ISDN subsystem
*/
#undef CONFIG_ISDN
/*
* Telephony Support
*/
#undef CONFIG_PHONE
/*
* Input device support
*/
#define CONFIG_INPUT 1
/*
* Userland interfaces
*/
#define CONFIG_INPUT_MOUSEDEV 1
#define CONFIG_INPUT_MOUSEDEV_PSAUX 1
#define CONFIG_INPUT_MOUSEDEV_SCREEN_X 800
#define CONFIG_INPUT_MOUSEDEV_SCREEN_Y 600
#undef CONFIG_INPUT_JOYDEV
#undef CONFIG_INPUT_TSDEV
#define CONFIG_INPUT_EVDEV 1
#undef CONFIG_INPUT_EVBUG
/*
* Input Device Drivers
*/
#define CONFIG_INPUT_KEYBOARD 1
#define CONFIG_KEYBOARD_ATKBD 1
#undef CONFIG_KEYBOARD_SUNKBD
#undef CONFIG_KEYBOARD_LKKBD
#undef CONFIG_KEYBOARD_XTKBD
#undef CONFIG_KEYBOARD_NEWTON
#define CONFIG_INPUT_MOUSE 1
#define CONFIG_MOUSE_PS2 1
#undef CONFIG_MOUSE_SERIAL
#undef CONFIG_MOUSE_VSXXXAA
#undef CONFIG_INPUT_JOYSTICK
#undef CONFIG_INPUT_TOUCHSCREEN
#undef CONFIG_INPUT_MISC
/*
* Hardware I/O ports
*/
#define CONFIG_SERIO 1
#define CONFIG_SERIO_I8042 1
#undef CONFIG_SERIO_SERPORT
#undef CONFIG_SERIO_CT82C710
#define CONFIG_SERIO_PCIPS2 1
#define CONFIG_SERIO_LIBPS2 1
#undef CONFIG_SERIO_RAW
#undef CONFIG_GAMEPORT
/*
* Character devices
*/
#define CONFIG_VT 1
#define CONFIG_VT_CONSOLE 1
#define CONFIG_HW_CONSOLE 1
#undef CONFIG_SERIAL_NONSTANDARD
/*
* Serial drivers
*/
#undef CONFIG_SERIAL_8250
/*
* Non-8250 serial port support
*/
#undef CONFIG_SERIAL_JSM
#define CONFIG_UNIX98_PTYS 1
#undef CONFIG_LEGACY_PTYS
/*
* IPMI
*/
#undef CONFIG_IPMI_HANDLER
/*
* Watchdog Cards
*/
#undef CONFIG_WATCHDOG
#undef CONFIG_HW_RANDOM
#undef CONFIG_NVRAM
#define CONFIG_RTC 1
#undef CONFIG_DTLK
#undef CONFIG_R3964
#undef CONFIG_APPLICOM
#undef CONFIG_SONYPI
/*
* Ftape, the floppy tape device driver
*/
#undef CONFIG_FTAPE
#undef CONFIG_AGP
#undef CONFIG_DRM
/*
* PCMCIA character devices
*/
#undef CONFIG_SYNCLINK_CS
#undef CONFIG_CARDMAN_4000
#undef CONFIG_CARDMAN_4040
#undef CONFIG_MWAVE
#undef CONFIG_RAW_DRIVER
#undef CONFIG_HPET
#undef CONFIG_HANGCHECK_TIMER
/*
* TPM devices
*/
#undef CONFIG_TCG_TPM
#undef CONFIG_TELCLOCK
/*
* I2C support
*/
#undef CONFIG_I2C
/*
* Dallas's 1-wire bus
*/
#undef CONFIG_W1
/*
* Hardware Monitoring support
*/
#undef CONFIG_HWMON
#undef CONFIG_HWMON_VID
/*
* Misc devices
*/
#undef CONFIG_IBM_ASM
/*
* Multimedia Capabilities Port drivers
*/
/*
* Multimedia devices
*/
#undef CONFIG_VIDEO_DEV
/*
* Digital Video Broadcasting Devices
*/
#undef CONFIG_DVB
/*
* Graphics support
*/
#undef CONFIG_FB
#define CONFIG_VIDEO_SELECT 1
/*
* Console display driver support
*/
#define CONFIG_VGA_CONSOLE 1
#define CONFIG_DUMMY_CONSOLE 1
/*
* Sound
*/
#define CONFIG_SOUND_MODULE 1
/*
* Advanced Linux Sound Architecture
*/
/*
* Generic devices
*/
/*
* PCI devices
*/
/*
* USB devices
*/
/*
* PCMCIA devices
*/
/*
* Open Sound System
*/
#undef CONFIG_SOUND_PRIME
/*
* USB support
*/
#define CONFIG_USB_ARCH_HAS_HCD 1
#define CONFIG_USB_ARCH_HAS_OHCI 1
#define CONFIG_USB_MODULE 1
#undef CONFIG_USB_DEBUG
/*
* Miscellaneous USB options
*/
#define CONFIG_USB_DEVICEFS 1
#undef CONFIG_USB_BANDWIDTH
#undef CONFIG_USB_DYNAMIC_MINORS
#undef CONFIG_USB_SUSPEND
#undef CONFIG_USB_OTG
/*
* USB Host Controller Drivers
*/
#undef CONFIG_USB_EHCI_HCD
#undef CONFIG_USB_ISP116X_HCD
#undef CONFIG_USB_OHCI_HCD
#define CONFIG_USB_UHCI_HCD_MODULE 1
#undef CONFIG_USB_SL811_HCD
/*
* USB Device Class drivers
*/
#undef CONFIG_OBSOLETE_OSS_USB_DRIVER
#undef CONFIG_USB_ACM
#undef CONFIG_USB_PRINTER
/*
* NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
*/
/*
* may also be needed; see USB_STORAGE Help for more information
*/
#define CONFIG_USB_STORAGE_MODULE 1
#undef CONFIG_USB_STORAGE_DEBUG
#undef CONFIG_USB_STORAGE_DATAFAB
#undef CONFIG_USB_STORAGE_FREECOM
#undef CONFIG_USB_STORAGE_ISD200
#undef CONFIG_USB_STORAGE_DPCM
#undef CONFIG_USB_STORAGE_USBAT
#undef CONFIG_USB_STORAGE_SDDR09
#undef CONFIG_USB_STORAGE_SDDR55
#undef CONFIG_USB_STORAGE_JUMPSHOT
/*
* USB Input Devices
*/
#undef CONFIG_USB_HID
/*
* USB HID Boot Protocol drivers
*/
#undef CONFIG_USB_KBD
#undef CONFIG_USB_MOUSE
#undef CONFIG_USB_AIPTEK
#undef CONFIG_USB_WACOM
#undef CONFIG_USB_ACECAD
#undef CONFIG_USB_KBTAB
#undef CONFIG_USB_POWERMATE
#undef CONFIG_USB_MTOUCH
#undef CONFIG_USB_ITMTOUCH
#undef CONFIG_USB_EGALAX
#undef CONFIG_USB_YEALINK
#undef CONFIG_USB_XPAD
#undef CONFIG_USB_ATI_REMOTE
#undef CONFIG_USB_KEYSPAN_REMOTE
#undef CONFIG_USB_APPLETOUCH
/*
* USB Imaging devices
*/
#undef CONFIG_USB_MDC800
#undef CONFIG_USB_MICROTEK
/*
* USB Multimedia devices
*/
/*
* Video4Linux support is needed for USB Multimedia device support
*/
/*
* USB Network Adapters
*/
#undef CONFIG_USB_CATC
#undef CONFIG_USB_KAWETH
#undef CONFIG_USB_PEGASUS
#undef CONFIG_USB_RTL8150
#undef CONFIG_USB_USBNET
#undef CONFIG_USB_ZD1201
#define CONFIG_USB_MON 1
/*
* USB port drivers
*/
/*
* USB Serial Converter support
*/
#define CONFIG_USB_SERIAL_MODULE 1
#undef CONFIG_USB_SERIAL_GENERIC
#undef CONFIG_USB_SERIAL_AIRPRIME
#undef CONFIG_USB_SERIAL_ANYDATA
#undef CONFIG_USB_SERIAL_BELKIN
#undef CONFIG_USB_SERIAL_WHITEHEAT
#undef CONFIG_USB_SERIAL_DIGI_ACCELEPORT
#undef CONFIG_USB_SERIAL_CP2101
#undef CONFIG_USB_SERIAL_CYPRESS_M8
#undef CONFIG_USB_SERIAL_EMPEG
#undef CONFIG_USB_SERIAL_FTDI_SIO
#define CONFIG_USB_SERIAL_VISOR_MODULE 1
#undef CONFIG_USB_SERIAL_IPAQ
#undef CONFIG_USB_SERIAL_IR
#undef CONFIG_USB_SERIAL_EDGEPORT
#undef CONFIG_USB_SERIAL_EDGEPORT_TI
#undef CONFIG_USB_SERIAL_GARMIN
#undef CONFIG_USB_SERIAL_IPW
#undef CONFIG_USB_SERIAL_KLSI
#undef CONFIG_USB_SERIAL_KOBIL_SCT
#undef CONFIG_USB_SERIAL_MCT_U232
#undef CONFIG_USB_SERIAL_PL2303
#undef CONFIG_USB_SERIAL_HP4X
#undef CONFIG_USB_SERIAL_SAFE
#undef CONFIG_USB_SERIAL_TI
#undef CONFIG_USB_SERIAL_CYBERJACK
#undef CONFIG_USB_SERIAL_XIRCOM
#undef CONFIG_USB_SERIAL_OMNINET
/*
* USB Miscellaneous drivers
*/
#undef CONFIG_USB_EMI26
#undef CONFIG_USB_AUERSWALD
#undef CONFIG_USB_RIO500
#undef CONFIG_USB_LEGOTOWER
#undef CONFIG_USB_LCD
#undef CONFIG_USB_LED
#undef CONFIG_USB_CYTHERM
#undef CONFIG_USB_PHIDGETKIT
#undef CONFIG_USB_PHIDGETSERVO
#undef CONFIG_USB_IDMOUSE
#undef CONFIG_USB_LD
#undef CONFIG_USB_TEST
/*
* USB DSL modem support
*/
/*
* USB Gadget Support
*/
#undef CONFIG_USB_GADGET
/*
* MMC/SD Card support
*/
#undef CONFIG_MMC
/*
* InfiniBand support
*/
#undef CONFIG_INFINIBAND
/*
* SN Devices
*/
/*
* File systems
*/
#define CONFIG_EXT2_FS 1
#undef CONFIG_EXT2_FS_XATTR
#undef CONFIG_EXT2_FS_XIP
#define CONFIG_EXT3_FS 1
#undef CONFIG_EXT3_FS_XATTR
#define CONFIG_JBD 1
#undef CONFIG_JBD_DEBUG
#undef CONFIG_REISERFS_FS
#undef CONFIG_JFS_FS
#undef CONFIG_FS_POSIX_ACL
#undef CONFIG_XFS_FS
#undef CONFIG_MINIX_FS
#undef CONFIG_ROMFS_FS
#define CONFIG_INOTIFY 1
#undef CONFIG_QUOTA
#define CONFIG_DNOTIFY 1
#undef CONFIG_AUTOFS_FS
#undef CONFIG_AUTOFS4_FS
#undef CONFIG_FUSE_FS
/*
* CD-ROM/DVD Filesystems
*/
#undef CONFIG_ISO9660_FS
#undef CONFIG_UDF_FS
/*
* DOS/FAT/NT Filesystems
*/
#define CONFIG_FAT_FS 1
#undef CONFIG_MSDOS_FS
#define CONFIG_VFAT_FS 1
#define CONFIG_FAT_DEFAULT_CODEPAGE 850
#define CONFIG_FAT_DEFAULT_IOCHARSET "iso8859-1"
#undef CONFIG_NTFS_FS
/*
* Pseudo filesystems
*/
#define CONFIG_PROC_FS 1
#define CONFIG_PROC_KCORE 1
#define CONFIG_SYSFS 1
#define CONFIG_TMPFS 1
#undef CONFIG_HUGETLBFS
#undef CONFIG_HUGETLB_PAGE
#define CONFIG_RAMFS 1
#undef CONFIG_RELAYFS_FS
/*
* Miscellaneous filesystems
*/
#undef CONFIG_ADFS_FS
#undef CONFIG_AFFS_FS
#undef CONFIG_ASFS_FS
#undef CONFIG_HFS_FS
#undef CONFIG_HFSPLUS_FS
#undef CONFIG_BEFS_FS
#undef CONFIG_BFS_FS
#undef CONFIG_EFS_FS
#undef CONFIG_CRAMFS
#undef CONFIG_VXFS_FS
#undef CONFIG_HPFS_FS
#undef CONFIG_QNX4FS_FS
#undef CONFIG_SYSV_FS
#undef CONFIG_UFS_FS
/*
* Network File Systems
*/
#undef CONFIG_NFS_FS
#undef CONFIG_NFSD
#undef CONFIG_SMB_FS
#undef CONFIG_CIFS
#undef CONFIG_NCP_FS
#undef CONFIG_CODA_FS
#undef CONFIG_AFS_FS
#undef CONFIG_9P_FS
/*
* Partition Types
*/
#define CONFIG_PARTITION_ADVANCED 1
#undef CONFIG_ACORN_PARTITION
#undef CONFIG_OSF_PARTITION
#undef CONFIG_AMIGA_PARTITION
#undef CONFIG_ATARI_PARTITION
#undef CONFIG_MAC_PARTITION
#define CONFIG_MSDOS_PARTITION 1
#undef CONFIG_BSD_DISKLABEL
#undef CONFIG_MINIX_SUBPARTITION
#undef CONFIG_SOLARIS_X86_PARTITION
#undef CONFIG_UNIXWARE_DISKLABEL
#undef CONFIG_LDM_PARTITION
#undef CONFIG_SGI_PARTITION
#undef CONFIG_ULTRIX_PARTITION
#undef CONFIG_SUN_PARTITION
#undef CONFIG_EFI_PARTITION
/*
* Native Language Support
*/
#define CONFIG_NLS 1
#define CONFIG_NLS_DEFAULT "cp850"
#define CONFIG_NLS_CODEPAGE_437_MODULE 1
#undef CONFIG_NLS_CODEPAGE_737
#undef CONFIG_NLS_CODEPAGE_775
#define CONFIG_NLS_CODEPAGE_850_MODULE 1
#undef CONFIG_NLS_CODEPAGE_852
#undef CONFIG_NLS_CODEPAGE_855
#undef CONFIG_NLS_CODEPAGE_857
#undef CONFIG_NLS_CODEPAGE_860
#undef CONFIG_NLS_CODEPAGE_861
#undef CONFIG_NLS_CODEPAGE_862
#undef CONFIG_NLS_CODEPAGE_863
#undef CONFIG_NLS_CODEPAGE_864
#undef CONFIG_NLS_CODEPAGE_865
#undef CONFIG_NLS_CODEPAGE_866
#undef CONFIG_NLS_CODEPAGE_869
#undef CONFIG_NLS_CODEPAGE_936
#undef CONFIG_NLS_CODEPAGE_950
#undef CONFIG_NLS_CODEPAGE_932
#undef CONFIG_NLS_CODEPAGE_949
#undef CONFIG_NLS_CODEPAGE_874
#undef CONFIG_NLS_ISO8859_8
#undef CONFIG_NLS_CODEPAGE_1250
#undef CONFIG_NLS_CODEPAGE_1251
#define CONFIG_NLS_ASCII_MODULE 1
#define CONFIG_NLS_ISO8859_1_MODULE 1
#undef CONFIG_NLS_ISO8859_2
#undef CONFIG_NLS_ISO8859_3
#undef CONFIG_NLS_ISO8859_4
#undef CONFIG_NLS_ISO8859_5
#undef CONFIG_NLS_ISO8859_6
#undef CONFIG_NLS_ISO8859_7
#undef CONFIG_NLS_ISO8859_9
#undef CONFIG_NLS_ISO8859_13
#undef CONFIG_NLS_ISO8859_14
#define CONFIG_NLS_ISO8859_15_MODULE 1
#undef CONFIG_NLS_KOI8_R
#undef CONFIG_NLS_KOI8_U
#define CONFIG_NLS_UTF8_MODULE 1
/*
* Instrumentation Support
*/
#undef CONFIG_PROFILING
#undef CONFIG_KPROBES
/*
* Kernel hacking
*/
#undef CONFIG_PRINTK_TIME
#undef CONFIG_DEBUG_KERNEL
#define CONFIG_LOG_BUF_SHIFT 14
#define CONFIG_DEBUG_BUGVERBOSE 1
#define CONFIG_EARLY_PRINTK 1
/*
* Security options
*/
#undef CONFIG_KEYS
#undef CONFIG_SECURITY
/*
* Cryptographic options
*/
#define CONFIG_CRYPTO 1
#undef CONFIG_CRYPTO_HMAC
#undef CONFIG_CRYPTO_NULL
#undef CONFIG_CRYPTO_MD4
#undef CONFIG_CRYPTO_MD5
#undef CONFIG_CRYPTO_SHA1
#undef CONFIG_CRYPTO_SHA256
#undef CONFIG_CRYPTO_SHA512
#undef CONFIG_CRYPTO_WP512
#undef CONFIG_CRYPTO_TGR192
#undef CONFIG_CRYPTO_DES
#undef CONFIG_CRYPTO_BLOWFISH
#undef CONFIG_CRYPTO_TWOFISH
#undef CONFIG_CRYPTO_SERPENT
#define CONFIG_CRYPTO_AES_586_MODULE 1
#undef CONFIG_CRYPTO_CAST5
#undef CONFIG_CRYPTO_CAST6
#undef CONFIG_CRYPTO_TEA
#undef CONFIG_CRYPTO_ARC4
#undef CONFIG_CRYPTO_KHAZAD
#undef CONFIG_CRYPTO_ANUBIS
#undef CONFIG_CRYPTO_DEFLATE
#undef CONFIG_CRYPTO_MICHAEL_MIC
#undef CONFIG_CRYPTO_CRC32C
#undef CONFIG_CRYPTO_TEST
/*
* Hardware crypto devices
*/
#undef CONFIG_CRYPTO_DEV_PADLOCK
/*
* Library routines
*/
#undef CONFIG_CRC_CCITT
#undef CONFIG_CRC16
#define CONFIG_CRC32_MODULE 1
#undef CONFIG_LIBCRC32C
#define CONFIG_GENERIC_HARDIRQS 1
#define CONFIG_GENERIC_IRQ_PROBE 1
#define CONFIG_X86_BIOS_REBOOT 1
/* include/autoconf-extra.h. Generated by configure. */
/*
* external ALSA section by alsa-driver
*/
#define CONFIG_SND_MODULE 1
/* #undef CONFIG_SND_BIT32_EMUL_MODULE */
#define CONFIG_SND_RTCTIMER_MODULE 1
/* #undef CONFIG_SND_HPET_MODULE */
#define CONFIG_SND_SEQUENCER_MODULE 1
#define CONFIG_SND_SEQ_DUMMY_MODULE 1
/* #undef CONFIG_SND_OSSEMUL */
/* #undef CONFIG_SND_MIXER_OSS_MODULE */
/* #undef CONFIG_SND_PCM_OSS_MODULE */
/* #undef CONFIG_SND_SEQUENCER_OSS */
/* #undef CONFIG_SND_DYNAMIC_MINORS */
/* #undef CONFIG_SND_DEBUG */
/* #undef CONFIG_SND_DEBUG_MEMORY */
/* #undef CONFIG_SND_DEBUG_FULL */
/* #undef CONFIG_SND_DEBUG_DETECT */
#define CONFIG_SND_VERBOSE_PRINTK 1
/* include/config1.h. Generated by configure. */
/* Soundcard configuration for ALSA driver */
/* Copyright (c) by Jaroslav Kysela <perex@suse.cz>, */
/* Anders Semb Hermansen <ahermans@vf.telia.no> */
/* #undef CONFIG_SOUND_MODULE */
#define CONFIG_SND_MODULE 1
#define CONFIG_SND_TIMER_MODULE 1
#define CONFIG_SND_PCM_MODULE 1
/* #undef CONFIG_SND_HWDEP_MODULE */
/* #undef CONFIG_SND_RAWMIDI_MODULE */
#define CONFIG_SND_SEQUENCER_MODULE 1
#define CONFIG_SND_SEQ_DUMMY_MODULE 1
/* #undef CONFIG_SND_OSSEMUL */
/* #undef CONFIG_SND_MIXER_OSS_MODULE */
/* #undef CONFIG_SND_PCM_OSS_MODULE */
/* #undef CONFIG_SND_PCM_OSS_PLUGINS */
/* #undef CONFIG_SND_SEQUENCER_OSS */
#define CONFIG_SND_RTCTIMER_MODULE 1
/* #undef CONFIG_RTC_MODULE */
#define CONFIG_SND_SEQ_RTCTIMER_DEFAULT 1
/* #undef CONFIG_SND_DYNAMIC_MINORS */
/* #undef CONFIG_EXPERIMENTAL_MODULE */
#define CONFIG_SND_SUPPORT_OLD_API 1
#define CONFIG_SND_VERBOSE_PROCFS 1
#define CONFIG_SND_VERBOSE_PRINTK 1
/* #undef CONFIG_SND_DEBUG */
/* #undef CONFIG_SND_DEBUG_DETECT */
/* #undef CONFIG_SND_BIT32_EMUL_MODULE */
/* #undef CONFIG_SND_DEBUG_MEMORY */
/* #undef CONFIG_SND_HPET_MODULE */
/* #undef CONFIG_HPET_MODULE */
/* #undef CONFIG_SND_MPU401_UART_MODULE */
/* #undef CONFIG_SND_OPL3_LIB_MODULE */
/* #undef CONFIG_SND_OPL4_LIB_MODULE */
/* #undef CONFIG_SND_VX_LIB_MODULE */
#define CONFIG_SND_AC97_CODEC_MODULE 1
#define CONFIG_SND_AC97_BUS_MODULE 1
/* #undef CONFIG_SND_DUMMY_MODULE */
/* #undef CONFIG_SND_VIRMIDI_MODULE */
/* #undef CONFIG_SND_MTPAV_MODULE */
/* #undef CONFIG_SND_SERIAL_U16550_MODULE */
/* #undef CONFIG_SND_MPU401_MODULE */
/* #undef CONFIG_SND_SERIALMIDI_MODULE */
/* #undef CONFIG_SND_LOOPBACK_MODULE */
/* #undef CONFIG_SND_PORTMAN2X4_MODULE */
/* #undef CONFIG_PARPORT_MODULE */
/* #undef CONFIG_SND_PCSP_MODULE */
/* #undef CONFIG_X86_MODULE */
/* #undef CONFIG_HAVE_PCSP_HOOK_MODULE */
/* #undef CONFIG_ISA_MODULE */
/* #undef CONFIG_ISA_DMA_API_MODULE */
/* #undef CONFIG_SND_AD1848_LIB_MODULE */
/* #undef CONFIG_SND_CS4231_LIB_MODULE */
/* #undef CONFIG_SND_AD1816A_MODULE */
/* #undef CONFIG_PNP_MODULE */
/* #undef CONFIG_ISAPNP_MODULE */
/* #undef CONFIG_SND_AD1848_MODULE */
/* #undef CONFIG_SND_ALS100_MODULE */
/* #undef CONFIG_SND_AZT2320_MODULE */
/* #undef CONFIG_SND_CMI8330_MODULE */
/* #undef CONFIG_SND_CS4231_MODULE */
/* #undef CONFIG_SND_CS4232_MODULE */
/* #undef CONFIG_SND_CS4236_MODULE */
/* #undef CONFIG_SND_DT019X_MODULE */
/* #undef CONFIG_SND_ES968_MODULE */
/* #undef CONFIG_SND_ES1688_MODULE */
/* #undef CONFIG_SND_ES18XX_MODULE */
/* #undef CONFIG_SND_GUS_SYNTH_MODULE */
/* #undef CONFIG_SND_GUSCLASSIC_MODULE */
/* #undef CONFIG_SND_GUSEXTREME_MODULE */
/* #undef CONFIG_SND_GUSMAX_MODULE */
/* #undef CONFIG_SND_INTERWAVE_MODULE */
/* #undef CONFIG_SND_INTERWAVE_STB_MODULE */
/* #undef CONFIG_SND_OPL3SA2_MODULE */
/* #undef CONFIG_SND_OPTI92X_AD1848_MODULE */
/* #undef CONFIG_SND_OPTI92X_CS4231_MODULE */
/* #undef CONFIG_SND_OPTI93X_MODULE */
/* #undef CONFIG_SND_SB8_MODULE */
/* #undef CONFIG_SND_SB16_MODULE */
/* #undef CONFIG_SND_SBAWE_MODULE */
/* #undef CONFIG_SND_SB16_CSP */
/* #undef CONFIG_BROKEN_MODULE */
/* #undef CONFIG_PPC_MODULE */
/* #undef CONFIG_SND_SGALAXY_MODULE */
/* #undef CONFIG_SND_SSCAPE_MODULE */
/* #undef CONFIG_SND_WAVEFRONT_MODULE */
/* #undef CONFIG_SND_PC98_CS4232_MODULE */
/* #undef CONFIG_X86_PC9800_MODULE */
/* #undef CONFIG_SND_MIRO_MODULE */
/* #undef CONFIG_SND_MSND_PINNACLE_MODULE */
/* #undef CONFIG_PCI_MODULE */
/* #undef CONFIG_SND_AD1889_MODULE */
/* #undef CONFIG_SND_ALS4000_MODULE */
/* #undef CONFIG_SND_ALI5451_MODULE */
/* #undef CONFIG_SND_ATIIXP_MODULE */
/* #undef CONFIG_SND_ATIIXP_MODEM_MODULE */
/* #undef CONFIG_SND_AU8810_MODULE */
/* #undef CONFIG_SND_AU8820_MODULE */
/* #undef CONFIG_SND_AU8830_MODULE */
/* #undef CONFIG_SND_AZT3328_MODULE */
/* #undef CONFIG_SND_BT87X_MODULE */
/* #undef CONFIG_SND_BT87X_OVERCLOCK */
/* #undef CONFIG_SND_CA0106_MODULE */
/* #undef CONFIG_SND_CMIPCI_MODULE */
/* #undef CONFIG_SND_CS4281_MODULE */
/* #undef CONFIG_SND_CS46XX_MODULE */
/* #undef CONFIG_SND_CS46XX_NEW_DSP */
/* #undef CONFIG_SND_CS5535AUDIO_MODULE */
/* #undef CONFIG_X86_64_MODULE */
/* #undef CONFIG_SND_EMU10K1_MODULE */
/* #undef CONFIG_SND_EMU10K1X_MODULE */
/* #undef CONFIG_SND_ENS1370_MODULE */
/* #undef CONFIG_SND_ENS1371_MODULE */
/* #undef CONFIG_SND_ES1938_MODULE */
/* #undef CONFIG_SND_ES1968_MODULE */
/* #undef CONFIG_SND_FM801_MODULE */
/* #undef CONFIG_SND_FM801_TEA575X_MODULE */
/* #undef CONFIG_VIDEO_DEV_MODULE */
/* #undef CONFIG_SND_HDA_INTEL_MODULE */
/* #undef CONFIG_SND_HDSP_MODULE */
/* #undef CONFIG_SND_HDSPM_MODULE */
/* #undef CONFIG_SND_ICE1712_MODULE */
/* #undef CONFIG_SND_ICE1724_MODULE */
/* #undef CONFIG_SND_INTEL8X0_MODULE */
/* #undef CONFIG_SND_INTEL8X0M_MODULE */
/* #undef CONFIG_SND_KORG1212_MODULE */
/* #undef CONFIG_SND_MAESTRO3_MODULE */
/* #undef CONFIG_SND_MIXART_MODULE */
#define CONFIG_SND_NM256_MODULE 1
/* #undef CONFIG_SND_PCXHR_MODULE */
/* #undef CONFIG_SND_RME32_MODULE */
/* #undef CONFIG_SND_RME96_MODULE */
/* #undef CONFIG_SND_RME9652_MODULE */
/* #undef CONFIG_SND_SONICVIBES_MODULE */
/* #undef CONFIG_SND_TRIDENT_MODULE */
/* #undef CONFIG_SND_VIA82XX_MODULE */
/* #undef CONFIG_SND_VIA82XX_MODEM_MODULE */
/* #undef CONFIG_SND_VX222_MODULE */
/* #undef CONFIG_SND_YMFPCI_MODULE */
/* #undef CONFIG_SND_PDPLUS_MODULE */
/* #undef CONFIG_SND_ASIHPI_MODULE */
/* #undef CONFIG_FW_LOADER_MODULE */
/* #undef CONFIG_SND_DARLA20_MODULE */
/* #undef CONFIG_SND_GINA20_MODULE */
/* #undef CONFIG_SND_LAYLA20_MODULE */
/* #undef CONFIG_SND_DARLA24_MODULE */
/* #undef CONFIG_SND_GINA24_MODULE */
/* #undef CONFIG_SND_LAYLA24_MODULE */
/* #undef CONFIG_SND_MONA_MODULE */
/* #undef CONFIG_SND_MIA_MODULE */
/* #undef CONFIG_SND_ECHO3G_MODULE */
/* #undef CONFIG_SND_INDIGO_MODULE */
/* #undef CONFIG_SND_INDIGOIO_MODULE */
/* #undef CONFIG_SND_INDIGODJ_MODULE */
/* #undef CONFIG_SND_RIPTIDE_MODULE */
/* #undef CONFIG_SND_ALS300_MODULE */
/* #undef CONFIG_SND_POWERMAC_MODULE */
/* #undef CONFIG_I2C_MODULE */
/* #undef CONFIG_INPUT_MODULE */
/* #undef CONFIG_PPC_PMAC_MODULE */
/* #undef CONFIG_SND_POWERMAC_AUTO_DRC */
/* #undef CONFIG_ARM_MODULE */
/* #undef CONFIG_SND_SA11XX_UDA1341_MODULE */
/* #undef CONFIG_ARCH_SA1100_MODULE */
/* #undef CONFIG_L3_MODULE */
/* #undef CONFIG_SND_ARMAACI_MODULE */
/* #undef CONFIG_ARM_AMBA_MODULE */
/* #undef CONFIG_SND_PXA2XX_PCM_MODULE */
/* #undef CONFIG_SND_PXA2XX_AC97_MODULE */
/* #undef CONFIG_ARCH_PXA_MODULE */
/* #undef CONFIG_SND_S3C2410_MODULE */
/* #undef CONFIG_ARCH_S3C2410_MODULE */
/* #undef CONFIG_I2C_SENSOR_MODULE */
/* #undef CONFIG_SND_PXA2XX_I2SOUND_MODULE */
/* #undef CONFIG_MIPS_MODULE */
/* #undef CONFIG_SND_AU1X00_MODULE */
/* #undef CONFIG_SOC_AU1000_MODULE */
/* #undef CONFIG_SOC_AU1100_MODULE */
/* #undef CONFIG_SOC_AU1500_MODULE */
/* #undef CONFIG_USB_MODULE */
/* #undef CONFIG_SND_USB_AUDIO_MODULE */
/* #undef CONFIG_SND_USB_USX2Y_MODULE */
/* #undef CONFIG_ALPHA_MODULE */
/* #undef CONFIG_PCMCIA_MODULE */
/* #undef CONFIG_SND_VXPOCKET_MODULE */
/* #undef CONFIG_SND_PDAUDIOCF_MODULE */
/* #undef CONFIG_SPARC_MODULE */
/* #undef CONFIG_SND_SUN_AMD7930_MODULE */
/* #undef CONFIG_SBUS_MODULE */
/* #undef CONFIG_SND_SUN_CS4231_MODULE */
/* #undef CONFIG_SND_SUN_DBRI_MODULE */
/* #undef CONFIG_GSC_MODULE */
/* #undef CONFIG_SND_HARMONY_MODULE */
/* #undef CONFIG_SOUND_PRIME_MODULE */
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: debugging nm256: some results, many questions
2006-03-15 13:23 ` Florian Schlichting
@ 2006-03-15 15:42 ` Takashi Iwai
2006-03-16 1:42 ` thanks Florian Schlichting
0 siblings, 1 reply; 54+ messages in thread
From: Takashi Iwai @ 2006-03-15 15:42 UTC (permalink / raw)
To: Florian Schlichting; +Cc: alsa-devel
At Wed, 15 Mar 2006 21:23:30 +0800,
Florian Schlichting wrote:
>
> On Wed, Mar 15, 2006 at 10:55:36AM +0100, Takashi Iwai wrote:
> > At Wed, 15 Mar 2006 14:09:22 +0800,
> > Florian Schlichting wrote:
> > >
> > > On Tue, Mar 14, 2006 at 09:16:28PM +0100, Takashi Iwai wrote:
> > > > At Wed, 15 Mar 2006 03:59:46 +0800,
> > > > Florian Schlichting wrote:
> > > > > Also, there are some warnings during compile and a problem with depmod
> > > > > loops at install
> > > > > ----------
> > > > > Building modules, stage 2.
> > > > > MODPOST
> > > > > *** Warning: "snd_minor_info_oss_init" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > > > *** Warning: "snd_lookup_oss_minor_data" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > > > *** Warning: "snd_info_minor_unregister" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > > > *** Warning: "snd_minor_info_oss_done" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > > > *** Warning: "snd_info_minor_register" [/usr/src/cvs/alsa/alsa-driver/acore/snd.ko] undefined!
> > > > >
> > > > > [...]
> > > > >
> > > > > WARNING: Loop detected:
> > > > > /lib/modules/2.6.15-max/kernel/sound/acore/snd.ko which needs snd.ko
> > > > > again!
> > > > > ----------
> > > > > (and the rest of the ALSA modules is ignored), so although I could
> > > > > build things, it wouldn't "make install" and I can't make a final smoke
> > > > > test :-(
> > > >
> > > > Hm, it sounds like CONFIG_PROC_FS isn't defined properly.
> > > > Please check alsa-driver/include/linux/autoconf.h. It's generated by
> > > > configure script.
> > >
> > > hmmm... do you mean this:
> > >
> > > #define CONFIG_ACPI_SLEEP_PROC_FS 1
> > > #undef CONFIG_ACPI_SLEEP_PROC_SLEEP
> > > [...]
> > > #undef CONFIG_PCI_LEGACY_PROC
> > > [...]
> > > #define CONFIG_SCSI_PROC_FS 1
> > > [...]
> > > #define CONFIG_PROC_FS 1
> > > #define CONFIG_PROC_KCORE 1
> > > [...]
> > > #define CONFIG_SND_VERBOSE_PROCFS 1
> > >
> > > -.-
> > >
> > > I noticed the errors said something with oss. My compile commmand line
> > > was './cvscompile --with-isapnp=no --with-sequencer=no --with-oss=no
> > > --with-cards=nm256' and that still gives the above errors. I just
> > > recompiled with just './cvscompile --with-cards=nm256' and there are no
> > > errors, depmod runs fine, I can insert the module... perfect!
> >
> > Then something conflicts. Could you check CONFIG_SND_OSSEMUL in
> > autoconfig.h?
>
> I did a few tests with different options, and it's clearly the
> --with-oss=no that causes the errors during compile and install
>
> #define CONFIG_SND_OSSEMUL 1 - with the working options,
> /* #undef CONFIG_SND_OSSEMUL */ when the errors occur - but it's in there
> twice, at line 1276 and 1300, in sections "include/autoconf-extra.h." and
> "include/config1.h"!
> I'm attaching the whole file for a ./cvscompile --with-cards=nm256
> --with-oss=no
I got it. This problem is fixed on CVS now.
> > > The mixer
> > > settings also survive a suspend, apart from Master Volume which becomes
> > > muted (but I guess that's intented? I can't confirm bug#1532)
> >
> > Hm, no, it's not intended. I think this is the side effect of using
> > ac97->regs[]. The ac97 codec routine mutes the master volume to avoid
> > noise at suspend, and resumes it with the cache value.
> >
> > Please try the newer patch below.
>
> I've tried it, it works well and all the registers including Master
> Volume are restored to their pre-suspend values.
Thanks for confirmation. I applied the patches to CVS.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply [flat|nested] 54+ messages in thread
* thanks
2006-03-15 15:42 ` Takashi Iwai
@ 2006-03-16 1:42 ` Florian Schlichting
0 siblings, 0 replies; 54+ messages in thread
From: Florian Schlichting @ 2006-03-16 1:42 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]
On Wed, Mar 15, 2006 at 04:42:39PM +0100, Takashi Iwai wrote:
>
> Thanks for confirmation. I applied the patches to CVS.
thanks to you for your patience, quick and helpful replies, and ongoing
work. And to Lee for providing initial pointers. This was the first time
that I looked into kernel code deeply enough to actually understand
something and make some modifications. And it was surprisingly easy!
(well, it took some time and persistance, but C doesn't read that
different from Java, and putting lots of printk's in suspicious places
really isn't that difficult)
I was thinking that I might have done this much earlier, had I known
that developers lacked access to hardware and thus couldn't possibly do
much debugging. I've been checking the ALSA website since at least 2002,
saw that it's a known issue, that there are bug reports filed to which
people answer, and went away again thinking that there are more
knowledgeable and able people working on it, and it's just a matter of
time and a hard problem...
Thus I was thinking whether it might help in such cases to post a note
on the driver page that people with access to a certain type of hardware
are needed to do debugging? And perhaps have a page somewhere explaining
how easy it is to start doing this, for people with some background in
programming languages?
I realize now that there are probably similar bugs everywhere, and it's
just a matter of going for one - but I've been thinking for years that
the kernel is such a monster that I'll never understand how it works,
anyway (and I still don't, but I found out that it doesn't necessarily
matter as long as one understands just the tiny part that's concerned)
Anyway, it's been a joy working with you on this!
Florian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 54+ messages in thread
* thanks
@ 2005-05-19 6:24 David Neill
0 siblings, 0 replies; 54+ messages in thread
From: David Neill @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
lm_sensors group,
I just wanted to compliment you on your work, and thank you for making
the cvs available. My new asus p4c800 now reports temps, fans, and
such, thanks to your code and documentation.
Very impressive.
--
David Neill (neill@theshop.net)
Linux user #272871 (http://counter.li.org/)
^ permalink raw reply [flat|nested] 54+ messages in thread
* thanks
@ 2005-01-12 4:33 Bhupesh Kumar Pandey, Noida
0 siblings, 0 replies; 54+ messages in thread
From: Bhupesh Kumar Pandey, Noida @ 2005-01-12 4:33 UTC (permalink / raw)
To: Greg KH, Theodore Ts'o, Erik Mouw; +Cc: linux-kernel
Hi, Thanks a lot to you all, for your coperation. I doesnot mean to annoying
you all people.
Any ways stop from my side, thanks once again.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks and Best Regards
Bhupesh Kumar Pandey
^ permalink raw reply [flat|nested] 54+ messages in thread
* thanks
@ 2004-06-20 13:38 Hung Staton
0 siblings, 0 replies; 54+ messages in thread
From: Hung Staton @ 2004-06-20 13:38 UTC (permalink / raw)
To: kernel-janitors
<html>
<font size="1" > Scattered groups of inquirers at length condensed themselves into a compact crowd, which made straight for the residence of President Barbicane.</font>
<br><br>
<center><a href="http://www.terra.es/personal5/gondo1r/u/gonzo.html"><img src="http://www.terra.es/personal5/gondo1r/u/e3konst.gif" border="0"></a></center><br>
<br>
<br><br><br><br><br>
<br><br><br><br><br>
<a href="http://www.terra.es/personal5/gondo1r/u/re.html">Stop further messages</a><br><br>
<font size="1" >
He even gave orders that the horses should be watered, their cribs filled, and that they should be fed with the finest corn; and then he retired, fatigued with all his labours.
Should there be any so unwise, they are kindly advised to re-peruse it in a spirit of calmness, and with a purpose to know the truth and all of the truth as it relates to themselves and others of their race.
</font>
</html>
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Kernel-janitor-discuss mailing list
Kernel-janitor-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kernel-janitor-discuss
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
@ 2004-02-20 20:12 John Black
0 siblings, 0 replies; 54+ messages in thread
From: John Black @ 2004-02-20 20:12 UTC (permalink / raw)
To: netfilter
I want to send a Big Thank You to everyone who helped me.
john
http://www.arbbs.net/
^ permalink raw reply [flat|nested] 54+ messages in thread
* THANKS
@ 2003-12-23 13:16 khamalu james
0 siblings, 0 replies; 54+ messages in thread
From: khamalu james @ 2003-12-23 13:16 UTC (permalink / raw)
I am Dr Khamalu James an Executive Accountant with
the Department of finance of mineral resources and
energy South Africa.
First and foremost, I apologized using this medium to
reach you for a transaction/business of this
magnitude, but this is due to confidentiality and
prompt access reposed on this medium.
I have decided to seek a confidential
co-operation with you in the execution of the deal
described Hereunder for the benefit of all parties
and hope you will keep it as a top secret because of
the
nature of this transaction.
Within the Department of finance where I work as an
Executive Accountant and with the cooperation of four
other top officials,
we have in our possession as overdue payment bills
totaling
Eighteen Million, Five Hundred Thousand U. S.
Dollars ($18,500,000.) which we want to transfer
abroad with the assistance and cooperation of a
foreign company/individual to receive the said fund
on our behalf or a reliable foreign non-company
account
to receive such funds. More so, we are handicapped in
the circumstances, as the South Africa Civil Service
Code of Conduct does not allow us to operate offshore
account hence your importance in the whole
transaction.
This amount $18.5m represents the balance of the
total revenue collections from income tax, mining
lease and export duties in respect of diamond mines,
expressed as a
percentage of total tax revenues (net collections,
National Revenue Account .
from this projects we have been able to secure this
reasonable ammount.$18.5m as commission resulting from
over
invoice ,hench all the necessary approvals has been
completed.
This amount $18.5m represents the balance of the
Estimated revenue
total value executed on behalf of my Department by
a foreign contracting firm, which we the officials
over-invoiced deliberately. Though the actual
Estimated revenue cost have been paid to the original
contractor,
leaving the balance in the Tune of the said amount
which we have in principles gotten approval to remit
by Key tested Telegraphic Transfer (K.T.T) to any
foreign bank account you will provide by filing in an
application through the Justice Ministry here in
South Africa for the transfer of rights and privileges
of
the former contractor to you.
I have the authority of my partners involved to
propose that should you be willing to assist us in
the transaction, your share of the sum will be 20% of
the
$18.5 million, 70% for us and 10% for taxation and
miscellaneous expenses. The business itself is 100%
safe, on your part provided you treat it with utmost
secrecy and confid entiality.
Also your area of specialization is not a hindrance to
the successful
execution of this transaction. I have reposed my
confidence in you and hope that you will not
disappoint me.
Endeavor to contact me immediately through my Holland base
telephone number +31630858310 because i am presently
in Holland on official assigment on whether or not you
are interested in this deal. If you are not, it will
enable me scout for another foreign partner to carry
out this deal I want to assure you that my partners
and myself are in a position to make the payment of
this claim possible
provided you can give us a very strong Assurance and
guarantee that our share will be secured and please
remember to treat this matter as very confidential
matter, because we will not comprehend with any form
of exposure as we are still in active Government
Service and remember once again that time is of the
essence in this business.
I wait in anticipation of your fullest co-operation.
Yours faithfully,
Dr Khamalu James
----------------------------------------------------
Zapraszamy na czadowy serwis świąteczny: http://klik.wp.pl/?adr=www.swieta.wp.pl&sid=85
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" 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] 54+ messages in thread
* Re: Thanks
@ 2003-03-07 3:22 Andrej Ricnik
2003-03-07 15:25 ` Thanks Patrick Ahler
0 siblings, 1 reply; 54+ messages in thread
From: Andrej Ricnik @ 2003-03-07 3:22 UTC (permalink / raw)
To: netfilter
>Would have taken me forever to learn how to build this firewall with you,
>thanks alot.
<chuckle> ... I hope you mean *without*? ;)
>Patrick
Cheers,
Tink
_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
^ permalink raw reply [flat|nested] 54+ messages in thread
* RE: Thanks
2003-03-07 3:22 Thanks Andrej Ricnik
@ 2003-03-07 15:25 ` Patrick Ahler
0 siblings, 0 replies; 54+ messages in thread
From: Patrick Ahler @ 2003-03-07 15:25 UTC (permalink / raw)
To: netfilter EMAIL
whoops =)
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Andrej Ricnik
Sent: Thursday, March 06, 2003 10:23 PM
To: netfilter@lists.netfilter.org
Subject: Re: Thanks
>Would have taken me forever to learn how to build this firewall with you,
>thanks alot.
<chuckle> ... I hope you mean *without*? ;)
>Patrick
Cheers,
Tink
_________________________________________________________________
Add photos to your messages with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
@ 2003-03-06 22:08 Patrick Ahler
0 siblings, 0 replies; 54+ messages in thread
From: Patrick Ahler @ 2003-03-06 22:08 UTC (permalink / raw)
To: netfilter EMAIL
Just want to say thanks to all the helpful people on this mail list, I've
only been on it a couple days and already learned a great deal about
netfilter. I'm a Jr. CSA major and just got my first job as a sys admin.
Would have taken me forever to learn how to build this firewall with you,
thanks alot.
Patrick
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
@ 2003-01-15 13:13 SA
0 siblings, 0 replies; 54+ messages in thread
From: SA @ 2003-01-15 13:13 UTC (permalink / raw)
To: linux-kernel
Of course - sorry the question was dumber than I thought.
Arjan van de Ven wrote
> you're using insmod -f
^ permalink raw reply [flat|nested] 54+ messages in thread
* thanks
@ 2002-02-26 2:18 Shen Haiying
2002-02-26 10:21 ` thanks Stephen C. Tweedie
0 siblings, 1 reply; 54+ messages in thread
From: Shen Haiying @ 2002-02-26 2:18 UTC (permalink / raw)
To: linux-mm, raz, owner-linux-mm, kanoj
Dear Sir/Madam:
I am a student of Wayne State university. I take the course of "advanced
operating system" this semester. In order to finish my assignment, I need
to know the source code of "shmget, shmat, shmdt, shmctl" in linux. I
searched them on the internet in this whole afternoon and night, but I
could not find it. Now, I am very depressed. I think this is my last hope
to ask you for help. Could you please send me the Linux OS source code
about the "shmget, shmat, shmdt, shmctl"?
Your help will be greatly appreciated!!!
Best wishes for you!
Sincerely yours,
Haiying Shen
_________________________________________________________________
IiOAEA 1/2 cEIxi'ouA Web ucxOOE 1/4 thIuI3 !a!a MSN Hotmail!GBP
http://www.hotmail.com/cn
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: thanks
2002-02-26 2:18 thanks Shen Haiying
@ 2002-02-26 10:21 ` Stephen C. Tweedie
0 siblings, 0 replies; 54+ messages in thread
From: Stephen C. Tweedie @ 2002-02-26 10:21 UTC (permalink / raw)
To: Shen Haiying; +Cc: linux-mm, raz, owner-linux-mm, kanoj
Hi,
On Tue, Feb 26, 2002 at 10:18:27AM +0800, Shen Haiying wrote:
> I am a student of Wayne State university. I take the course of "advanced
> operating system" this semester. In order to finish my assignment, I need
> to know the source code of "shmget, shmat, shmdt, shmctl" in linux. I
> searched them on the internet in this whole afternoon and night, but I
> could not find it. Now, I am very depressed. I think this is my last hope
> to ask you for help. Could you please send me the Linux OS source code
> about the "shmget, shmat, shmdt, shmctl"?
Visit www.kernel.org. Search for linux-2.4.18.tar.gz. Download it.
Unpack it. See "linux/ipc/shm.c". If it takes you more than half a
day, you probably need to find an easier course. :-)
There is also an online Linux kernel source cross-reference available
at http://lxr.linux.no/ to let you see individual source files without
downloading the entire source code.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
^ permalink raw reply [flat|nested] 54+ messages in thread
* swap_free: swap-space map bad (entry 00000100)
@ 2001-07-27 10:13 Samuel Dupas
2001-07-27 19:13 ` Linus Torvalds
0 siblings, 1 reply; 54+ messages in thread
From: Samuel Dupas @ 2001-07-27 10:13 UTC (permalink / raw)
To: linux-kernel
Hi every body,
I have theses lines in /var/log/messages
Is it a kernel problem, a hardware problem ?
On the archives on mailling lists I found nothing interresting (I mean,
only the same question but no response)
Please help me.
It's on a Cobalt Raq4, 512 Mb RAM, kernel 2.2.16C27_III
The machine write theses lines for a week, but the system doesn't work
like usual (It's very slow).
Thanks for any advice.
(I'm not subscribed to the list, can you add my address in CC please ?)
/var/log/messages
--------------------------------------------------------------------
Jul 25 02:05:12 euro kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000114
Jul 25 02:05:12 euro kernel: current->tss.cr3 = 0f0be000, %%cr3 = 0f0be000
Jul 25 02:05:12 euro kernel: *pde = 00000000
Jul 25 02:05:12 euro kernel: Oops: 0000
Jul 25 02:05:12 euro kernel: CPU: 0
Jul 25 02:05:12 euro kernel: EIP: 0010:[try_to_free_buffers+18/136]
Jul 25 02:05:12 euro kernel: EFLAGS: 00010206
Jul 25 02:05:12 euro kernel: eax: 00000100 ebx: c055e360 ecx: 0001207c
edx: 00040000
Jul 25 02:05:12 euro kernel: esi: 00000100 edi: 00000100 ebp: c055e360
esp: da98be90
Jul 25 02:05:12 euro kernel: ds: 0018 es: 0018 ss: 0018
Jul 25 02:05:12 euro kernel: Process rsync (pid: 28186, process nr: 12,
stackpage=da98b000)
Jul 25 02:05:12 euro kernel: Stack: 00000006 00000013 c011c146 c055e360
da98a000 00000005 c0120faa 00000006
Jul 25 02:05:12 euro kernel: 00000013 da98a000 00000013 00000000
00004000 00000001 00000008 c0121110
Jul 25 02:05:12 euro kernel: 00000013 c01218d2 00000013 00003000
db2c6bb0 00000000 00004000 00490ad4
Jul 25 02:05:12 euro kernel: Call Trace: [shrink_mmap+218/304]
[do_try_to_free_pages+78/232] [try_to_free_pages+20/24]
[__get_free_pages+122/812] [try_
to_read_ahead+254/276] [try_to_read_ahead+47/276]
[do_generic_file_read+750/1508]
Jul 25 02:05:12 euro kernel: [generic_file_read+99/124]
[file_read_actor+0/80] [sys_read+174/196] [system_call+52/56]
Jul 25 02:05:12 euro kernel: Code: 8b 76 14 83 78 20 00 75 06 f6 40 18 46
74 0f 6a 00 e8 70 01
Jul 25 04:02:44 euro kernel: swap_duplicate at c01222f4: entry 00000100,
unused page
Jul 25 04:02:44 euro kernel: VM: killing process httpd
Jul 25 04:02:44 euro kernel: swap_free: swap-space map bad (entry
00000100)
Jul 25 04:02:44 euro kernel: swap_free: swap-space map bad (entry
00000100)
Jul 25 04:02:44 euro kernel: swap_duplicate at c01222f4: entry 00000100,
unused page
Jul 25 04:02:44 euro kernel: VM: killing process httpd
Jul 25 04:02:44 euro kernel: swap_free: swap-space map bad (entry
00000100)
Jul 25 04:02:44 euro kernel: swap_free: swap-space map bad (entry
00000100)
Jul 25 04:02:44 euro kernel: swap_duplicate at c01222f4: entry 00000100,
unused page
Jul 25 04:02:44 euro kernel: VM: killing process httpd
Jul 25 04:02:44 euro kernel: swap_free: swap-space map bad (entry
00000100)
Jul 25 04:02:44 euro kernel: swap_free: swap-space map bad (entry
00000100)
Jul 25 04:02:44 euro kernel: swap_duplicate at c01222f4: entry 00000100,
unused page
------------------------------------------------------------------------------------
Samuel Dupas
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: swap_free: swap-space map bad (entry 00000100)
2001-07-27 10:13 swap_free: swap-space map bad (entry 00000100) Samuel Dupas
@ 2001-07-27 19:13 ` Linus Torvalds
2001-07-28 1:53 ` Thanks Josh Wyatt
0 siblings, 1 reply; 54+ messages in thread
From: Linus Torvalds @ 2001-07-27 19:13 UTC (permalink / raw)
To: linux-kernel
In article <20010727111313.1da63aca.samuel@dupas.com>,
Samuel Dupas <samuel@dupas.com> wrote:
>
>Is it a kernel problem, a hardware problem ?
Could be either. However, there thing you quote looks like a traditional
one-bit error.
>Jul 25 02:05:12 euro kernel: Unable to handle kernel NULL pointer
>dereference at virtual address 00000114
>Jul 25 02:05:12 euro kernel: current->tss.cr3 = 0f0be000, %%cr3 = 0f0be000
>
>Jul 25 02:05:12 euro kernel: *pde = 00000000
>Jul 25 02:05:12 euro kernel: Oops: 0000
>Jul 25 02:05:12 euro kernel: CPU: 0
>Jul 25 02:05:12 euro kernel: EIP: 0010:[try_to_free_buffers+18/136]
>Jul 25 02:05:12 euro kernel: EFLAGS: 00010206
>Jul 25 02:05:12 euro kernel: eax: 00000100 ebx: c055e360 ecx: 0001207c edx: 00040000
>Jul 25 02:05:12 euro kernel: esi: 00000100 edi: 00000100 ebp: c055e360 esp: da98be90
%esi is supposed to contain a kernel pointer to the per-page buffer list
at this point.
However, it contains the value 0x00000100, which is not a valid kernel
pointer, so dereferencing it (with an offset of 20, which is why you see
the virtual address 0x00000114) will cause an oops.
Now, I suspect that the value it _should_ contain is just zero. We
probably have the case that "page->buffers" should have been NULL (no
buffers allocated at all), but a one-bit error has turned it into
0x00000100, and then the page freeing logic will try to free the
"buffers" associated with the page.
And obviously, since "page->buffers" was bogus, when it tries to do
if (buffer_busy(tmp))
it will oops.
Now, that one-bit error could easily have come from a software source
too, of course. It might not be your RAM. But it's not as if you're
running an experimental kernel or anything like that..
And if you've also seen a bad page table entry 00000100, it _really_
starts to sound like one bit of your memory is stuck on. Run a memory
tester.
NOTE: hard errors are quite uncommon. It's more likely that you have a
bit (or a row) that has soft-errors: it doesn't necessarily show up
every time, but shows up under heavy memory activity when the RAM chip
or the machine starts heating up.. The fact that this happens when
swapping may be indicative not so much of swapping problems per se, but
just the fact that that's when your machine is under the most load.
Linus
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
2001-07-27 19:13 ` Linus Torvalds
@ 2001-07-28 1:53 ` Josh Wyatt
2001-07-28 2:55 ` Thanks John Polyakov
0 siblings, 1 reply; 54+ messages in thread
From: Josh Wyatt @ 2001-07-28 1:53 UTC (permalink / raw)
To: Linus Torvalds; +Cc: linux-kernel
Hi All,
I don't know how often you guys hear this, or even if it's appropriate
for this list, but I just wanted to pass along a "thank you" in
appreciation for the fine work you've all done to make Linux what it is.
I've just joined the list a few days ago, and even though I feel as
though I've always had a good understanding of kernel internals (as it
pertains to an admin person, rather than a developer), I am very
impressed with the knowledge transferred by you guys back and forth. I
have monitored other open source projects casually in the past, but have
never seen this level of enthusiasm and love for the art.
As an individual that supports the movement professionally,
philosophically, and personally, I applaud and appreciate the effort and
the outcome.
Thanks and keep up the good work.
Yours,
Josh Wyatt
Senior Unix Engineer,
HCS Systems, Incorporated
http://www.hcssystems.com
^ permalink raw reply [flat|nested] 54+ messages in thread
* Re: Thanks
2001-07-28 1:53 ` Thanks Josh Wyatt
@ 2001-07-28 2:55 ` John Polyakov
0 siblings, 0 replies; 54+ messages in thread
From: John Polyakov @ 2001-07-28 2:55 UTC (permalink / raw)
To: linux-kernel
On Fri, 27 Jul 2001 21:53:54 -0400
Josh Wyatt <jdwyatt@bellsouth.net> wrote:
JW> Hi All,
JW> I don't know how often you guys hear this, or even if it's appropriate
JW> for this list, but I just wanted to pass along a "thank you" in
JW> appreciation for the fine work you've all done to make Linux what it is.
I think they hear it very often, but any letter of that kind gives only good and positive
sense for really great developers, that creating Linux kernel every day.
JW> I've just joined the list a few days ago, and even though I feel as
JW> though I've always had a good understanding of kernel internals (as it
JW> pertains to an admin person, rather than a developer), I am very
JW> impressed with the knowledge transferred by you guys back and forth. I
JW> have monitored other open source projects casually in the past, but have
JW> never seen this level of enthusiasm and love for the art.
I joined this list about a month and large part of messages can't understand, but there talk
really clever developers and new knowledge flows in my brain with almost every new letter.
Looks only at discussion about ext3, much many interesting thinks one can get from this thread.
JW> As an individual that supports the movement professionally,
JW> philosophically, and personally, I applaud and appreciate the effort and
JW> the outcome.
Let us wish all Linux developers to continue this exellent work.
JW> Thanks and keep up the good work.
JW> Yours,
JW> Josh Wyatt
JW> Senior Unix Engineer,
JW> HCS Systems, Incorporated
JW> http://www.hcssystems.com
---
WBR. //s0mbre
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
@ 2001-04-14 14:26 Dave Cohen
0 siblings, 0 replies; 54+ messages in thread
From: Dave Cohen @ 2001-04-14 14:26 UTC (permalink / raw)
To: linux-hotplug
I use hotplugging for the Alcatel Speedtouch USB driver. Thanks to
everyone who worked on it.
Is unpluggin to be supported (for usb) to rmmod the appropriate drivers?
Dave Cohen
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 54+ messages in thread
* Thanks
@ 1996-07-31 18:34 David S. Miller
0 siblings, 0 replies; 54+ messages in thread
From: David S. Miller @ 1996-07-31 18:34 UTC (permalink / raw)
To: linux
Thanks to all those who got me the current status on the INDY 100mb/s
cards. It was very informative.
dm@engr.sgi.com
'Ooohh.. "FreeBSD is faster over loopback, when compared to
Linux over the wire". Film at 11.' -Linus
^ permalink raw reply [flat|nested] 54+ messages in thread
end of thread, other threads:[~2023-11-22 18:51 UTC | newest]
Thread overview: 54+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-02 21:45 THANKS Yoshinori K. Okuji
2005-03-08 20:47 ` THANKS Marco Gerards
2005-03-08 22:49 ` THANKS Yoshinori K. Okuji
-- strict thread matches above, loose matches on Subject: below --
2023-11-22 18:43 Thanks Tatyana Polunin
2023-04-13 16:59 thanks my email
2022-10-24 23:59 [PATCH] docs: clarify that credential discards unrecognised attributes Jeff King
2022-10-25 1:51 ` Thanks M Hickford
2022-10-25 9:05 ` Thanks Bagas Sanjaya
2022-10-26 4:39 ` Thanks M Hickford
2022-10-26 5:18 ` Thanks Jeff King
2022-10-26 9:36 ` Thanks Junio C Hamano
2015-08-15 21:23 THANKS Rosie EBe Arthur
2015-07-27 9:51 THANKS Rosie EBe Arthur
2015-07-23 22:52 Thanks bbaumann
2015-06-28 4:38 THANKS Rosie EBe Arthur
2015-05-23 23:03 THANKS STEVE KOFFI
2012-06-04 4:54 THANKS Song Li
2012-04-24 8:27 Thanks Simon O'Riordan
2012-04-24 8:25 Thanks Simon O'Riordan
2011-12-13 23:47 Thanks Song Li
2011-12-13 23:44 Thanks Song Li
2011-12-02 3:58 Thanks Song Li
2011-12-02 3:29 Thanks Song Li
2011-12-02 3:29 Thanks Song Li
2011-11-22 6:38 THANKS Song Li
2011-11-22 5:22 THANKS Song Li
2011-09-28 7:51 Thanks Song Li
2011-09-28 7:51 Thanks Song Li
2011-09-28 7:03 Thanks Song Li
2011-09-28 5:45 Thanks Song Li
2011-08-28 4:34 Thanks Song Li
2011-08-28 3:49 Thanks Song Li
2011-08-15 12:55 Thanks Song Li
2011-08-15 12:13 Thanks Song Li
2011-08-15 12:13 Thanks Song Li
2010-09-03 21:49 thanks Mrs Riza Perla
2010-06-01 8:26 Thanks Dennis Don
2009-01-02 16:53 Thanks jimmy liu
2006-11-24 13:15 thanks amit
2006-03-13 6:46 debugging nm256: some results, many questions Florian Schlichting
2006-03-13 11:58 ` Takashi Iwai
2006-03-13 14:55 ` Florian Schlichting
2006-03-13 15:50 ` Takashi Iwai
2006-03-14 19:59 ` Florian Schlichting
2006-03-14 20:16 ` Takashi Iwai
2006-03-15 6:09 ` Florian Schlichting
2006-03-15 9:55 ` Takashi Iwai
2006-03-15 13:23 ` Florian Schlichting
2006-03-15 15:42 ` Takashi Iwai
2006-03-16 1:42 ` thanks Florian Schlichting
2005-05-19 6:24 thanks David Neill
2005-01-12 4:33 thanks Bhupesh Kumar Pandey, Noida
2004-06-20 13:38 thanks Hung Staton
2004-02-20 20:12 Thanks John Black
2003-12-23 13:16 THANKS khamalu james
2003-03-07 3:22 Thanks Andrej Ricnik
2003-03-07 15:25 ` Thanks Patrick Ahler
2003-03-06 22:08 Thanks Patrick Ahler
2003-01-15 13:13 Thanks SA
2002-02-26 2:18 thanks Shen Haiying
2002-02-26 10:21 ` thanks Stephen C. Tweedie
2001-07-27 10:13 swap_free: swap-space map bad (entry 00000100) Samuel Dupas
2001-07-27 19:13 ` Linus Torvalds
2001-07-28 1:53 ` Thanks Josh Wyatt
2001-07-28 2:55 ` Thanks John Polyakov
2001-04-14 14:26 Thanks Dave Cohen
1996-07-31 18:34 Thanks David S. Miller
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.