From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: Script to build the media documentation as if it were a single book
Date: Thu, 16 Apr 2020 09:55:54 +0200 [thread overview]
Message-ID: <20200416095554.53566315@coco.lan> (raw)
In-Reply-To: <c55b5aae-ffb5-3ca0-b855-1df4a2da08f9@xs4all.nl>
Em Thu, 16 Apr 2020 09:29:45 +0200
Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> On 16/04/2020 09:21, Mauro Carvalho Chehab wrote:
> > Em Thu, 16 Apr 2020 09:01:55 +0200
> > Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> >
> >> On 14/04/2020 15:37, Mauro Carvalho Chehab wrote:
> >
> >>> ================================
> >>> Linux Kernel Media Documentation
> >>> ================================
> >>>
> >>> .. toctree::
> >>> :maxdepth: 4
> >>>
> >>> admin-guide/index
> >>> driver-api/index
> >>> userspace-api/index
> >>
> >> Wouldn't it make more sense to have the userspace-api before the admin-guide?
> >
> > There, I just placed them on alphabetic order.
> >
> > But answering your question, that depends on the audience ;-)
> >
> > -
> >
> > Yet, assuming that we are doing a good job, I would expect a lot more
> > users than developers[1].
>
> If you want to see what it looks like with userspace-api on top:
>
> https://hverkuil.home.xs4all.nl/spec/index.html
>
> I think it makes more sense that way.
With the current content, I fully agree with you. However, take a look
at the RFC patch I just sent. It is just the start of something
(and it is not aligned yet with the latest Kconfig changes).
Anyway, my plan is to add something that a random media user could
find some useful information, and point to our Wiki pages where
it would make sense.
>
> Regards,
>
> Hans
>
> >
> > [1] Granted, there are lots of gaps there for it to be a generic guide
> > to media subsystem. I'm planning to improve the admin-guide in order
> > to make it more consistent and useful for media users.
> >
> > The order there, IMHO, doesn't matter much, as someone accessing it from
> > LinuxTV.org would likely use this URL:
> >
> > https://linuxtv.org/docs.php
> >
> > Side note: I need to add a pointer to the admin guide there - and at the
> > wiki pages.
> >
> > Thanks,
> > Mauro
> >
>
Thanks,
Mauro
next prev parent reply other threads:[~2020-04-16 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 13:37 Script to build the media documentation as if it were a single book Mauro Carvalho Chehab
2020-04-16 7:01 ` Hans Verkuil
2020-04-16 7:21 ` Mauro Carvalho Chehab
2020-04-16 7:29 ` Hans Verkuil
2020-04-16 7:55 ` Mauro Carvalho Chehab [this message]
2020-04-16 8:06 ` Hans Verkuil
2020-04-16 9:02 ` Mauro Carvalho Chehab
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=20200416095554.53566315@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).