From: Jupiter <jupiter.hce@gmail.com>
To: tomzy <tomasz.zyjewski@3mdeb.com>
Cc: yocto <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Honister broken WiFi communication
Date: Wed, 19 Jan 2022 19:14:58 +1100 [thread overview]
Message-ID: <CAA=hcWRq75O-D-d+a30zg1AZRZvYd=wpUdGTK4GnhSeYsAVhaQ@mail.gmail.com> (raw)
In-Reply-To: <414.1642571736890055031@lists.yoctoproject.org>
Hi Tomasz,
Thanks for your response.
> Are you using custom Linux kernel / custom device tree? Maybe there is
> some issue there?
Yes, but the Zeus build image uses the same device tree that could run
WiFi connection without any issues, I am comparing the same source and
configuration between Zeus and Honister, the only difference is the
two different OE Yocto versions.
Thank you.
Kind regards,
- jh
next prev parent reply other threads:[~2022-01-19 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 9:53 Honister broken WiFi communication Jupiter
2022-01-18 15:31 ` [yocto] " Rudolf Streif
2022-01-19 1:45 ` Jupiter
2022-01-19 5:55 ` tomzy
2022-01-19 8:14 ` Jupiter [this message]
2022-01-20 1:01 ` [yocto] " Rudolf J Streif
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='CAA=hcWRq75O-D-d+a30zg1AZRZvYd=wpUdGTK4GnhSeYsAVhaQ@mail.gmail.com' \
--to=jupiter.hce@gmail.com \
--cc=tomasz.zyjewski@3mdeb.com \
--cc=yocto@lists.yoctoproject.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).