From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Quentin Schulz" <quentin.schulz@cherry.de>,
<chris.laplante@agilent.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] dev-manual/debugging: improve gdbserver debugfs docs
Date: Tue, 22 Oct 2024 14:21:48 +0200 [thread overview]
Message-ID: <D52BXCQFSKUK.52RDIPVCESOW@bootlin.com> (raw)
In-Reply-To: <fdc83afc-d274-4a90-8fbe-ef0717f099af@cherry.de>
On Tue Oct 22, 2024 at 2:17 PM CEST, Quentin Schulz wrote:
> Hi Antonin,
>
> On 10/22/24 2:10 PM, Antonin Godard wrote:
>> Hi Quentin,
>>
>> On Tue Oct 22, 2024 at 1:57 PM CEST, Quentin Schulz via lists.yoctoproject.org wrote:
>>>> 1. Make it clear that IMAGE_FSTYPES has to contain tar.bz2
>>>
>>> Yes, but isn't it done automatically if IMAGE_FSTYPES_DEBUGFS and
>>> IMAGE_GEN_DEBUGFS are set?
>>>
>>> We have a selftest here: meta/lib/oeqa/selftest/cases/gdbserver.py that
>>> doesn't seem to be adding tar.bz2 to IMAGE_FSTYPES, so I assume it's fine?
>>
>> I think it might be because qemu.inc adds it by default (not a oeqa expert
>> though :) ). Here's what I have by default with qemu:
>>
>> ```
>> $ bitbake-getvar IMAGE_FSTYPES -r core-image-minimal
>> #
>> # $IMAGE_FSTYPES [3 operations]
>> # append /build/../work/openembedded-core/meta/conf/machine/include/qemu.inc:18
>> # "tar.bz2 ext4"
>> # set /build/../work/openembedded-core/meta/conf/documentation.conf:215
>> # [doc] "Formats of root filesystem images that you want to have created."
>> # set? /build/../work/openembedded-core/meta/conf/bitbake.conf:844
>> # "tar.gz"
>> # pre-expansion value:
>> # " tar.bz2 ext4"
>> IMAGE_FSTYPES=" tar.bz2 ext4"
>> ```
>>
>>> meta/classes-recipe/image.bbclass and
>>> meta/classes-recipe/image_types.bbclass are the only places where
>>> IMAGE_FSTYPES_DEBUGFS is actually used, and it seems that we're adding
>>> the content of IMAGE_FSTYPES_DEBUGFS to those of IMAGE_FSTYPES if I am
>>> not misreading it?
>>
>> In image_types, the following:
>>
>> fstypes |= set((d.getVar('IMAGE_FSTYPES_DEBUGFS') or "").split())
>>
>> Is an union, so if tar.bz2 is not in IMAGE_FSTYPES it won't work actually.
>>
>
> It's a union, yes, but that's why it'll work :)
>
> >>> a = set([1, 2, 3])
> >>> b = set([3, 4, 5])
> >>> a | b
> {1, 2, 3, 4, 5}
> >>> c = set([5, 6, 7])
> >>> c |= a
> >>> c
> {1, 2, 3, 5, 6, 7}
>
> c.f. https://docs.python.org/3/library/stdtypes.html#frozenset.union
Indeed, my bad, read that too quickly. Thanks :)
Cheers,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-10-22 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 15:22 [PATCH] dev-manual/debugging: improve gdbserver debugfs docs chris.laplante
2024-10-21 19:54 ` [docs] " Adrian Freihofer
2024-10-22 8:19 ` Antonin Godard
2024-10-22 8:01 ` Antonin Godard
2024-10-22 11:57 ` Quentin Schulz
2024-10-22 12:10 ` Antonin Godard
2024-10-22 12:17 ` Quentin Schulz
2024-10-22 12:21 ` Antonin Godard [this message]
2024-10-22 14:39 ` chris.laplante
2024-10-22 14:52 ` Quentin Schulz
2024-10-22 19:59 ` chris.laplante
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=D52BXCQFSKUK.52RDIPVCESOW@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=chris.laplante@agilent.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
/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 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.