From: Robin Steven <armrobin@gmail.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can not generate ALSA driver documentation via Makefile
Date: Sun, 20 Dec 2009 02:46:19 +0800 [thread overview]
Message-ID: <8e678d3f0912191046i3c536f3at275d81a83c024571@mail.gmail.com> (raw)
In-Reply-To: <20091219102223.506c9e9c.rdunlap@xenotime.net>
Thanks, Dunlap:
Sorry for my negligence! the issue is on default kernel version 2.6.28
of my target embedded board,
now I get the document "writing-an-alsa-driver.html" via my Linux host
gentoo, it currently use
Kernel 2.6.31-gentoo-r31.
Best regard !
= Robin
On Sun, Dec 20, 2009 at 2:22 AM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Sat, 19 Dec 2009 18:14:33 +0800 Robin Steven wrote:
>
>> Hi, guy:
>>
>> I am hacking ALSA driver for my customized board, and want to study
>> the document "writing_an_alsa_driver" in
>> "Documentation/sound/alsa/DocBook", in the top directory of kernel
>> source and run:
>>
>> $ make htmldocs
>>
>> I can get all the html format document in "Documentation/DocBook", and
>> no any html document in
>> "Documentation/sound/alsa/DocBook" was converted for .tmpl to html.
>>
>> Thanks in advenced for any one can give me any idea!
>
> I guess it depends on what kernel version you are trying to use
> (and you omitted that info).
>
> With 2.6.32-git14, I see all of the input & generated alsa files
> under Documentation/DocBook/, including "writing_an_alsa_driver".
>
> Can you try a more recent (or current) kernel version?
>
> ---
> ~Randy
>
prev parent reply other threads:[~2009-12-19 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 10:14 Robin Steven
2009-12-19 18:22 ` Randy Dunlap
2009-12-19 18:46 ` Robin Steven [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8e678d3f0912191046i3c536f3at275d81a83c024571@mail.gmail.com \
--to=armrobin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®