Hi,
I looked at my kernel 5.1 defconfig and could not find device driver
for NAND Flash PARALLEL 48TSOP, any advice how to make the kernel
support for NAND Flash PARALLEL 48TSOP?
Thank you.
- jupiter
--
___
linux-yocto mailing list
[Re: v4.18.x - stable updates comprising v4.18.38] On 16/05/2019 (Thu 15:59)
Bruce Ashfield wrote:
>
>
> On Wed, May 15, 2019 at 6:07 PM Paul Gortmaker
> wrote:
>
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto
On Wed, May 15, 2019 at 6:07 PM Paul Gortmaker
wrote:
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto project, continuing from the previous v4.18.37 release.
>
> There is one trivial one line commit to fix a build error on
Both are now merged to master.
Bruce
On Wed, May 15, 2019 at 10:32 PM Mittal, Anuj wrote:
> Hi Bruce,
>
> Both these changes are only for master and are specific to v5.1.
>
> On Thu, 2019-05-16 at 10:26 +0800, Anuj Mittal wrote:
> > This has been removed starting v5.1 and nf_nat_ipv4,6 have
merged.
Bruce
On Tue, May 14, 2019 at 10:33 AM Daniel Dragomir <
daniel.drago...@windriver.com> wrote:
> Disabled correctable errors reporting for SYSMEM and CMEM by default.
>
> EDAC_AXXIA_SYSMEM_SKIP_CORRECTABLE:
> Support for deactivation of processing of SYSMEM correctable errors
> (single
merged.
SRCREV updates will follow with my next round of -stable bumps.
Bruce
On Tue, May 14, 2019 at 5:09 AM Liwei Song wrote:
> From: Takashi Iwai
>
> commit f495222e28275222ab6fd93813bd3d462e16d340 upstream.
>
> Currently the IRQ handler in HD-audio controller driver is registered
>
On Tue, May 14, 2019 at 9:18 AM Daniel Dragomir <
daniel.drago...@windriver.com> wrote:
> Hello Bruce!
>
> I know 4.1 is not supported anymore, but if possible,
> please review and merge this series of patches in
>
I'm still doing -stable updates when I can to 4.1 (I'm a bit behind at the
No, unfortunately not. HDMI works just fine but no video on the touch
display.
On 5/16/19 9:46 AM, Andrei Gherzan wrote:
Hi,
On 16/05/2019 17.24, Rudolf J Streif wrote:
Thank you, Paul. I did read Andrei's excellent documentation and
enabled I2C and SPI etc.
And it didn't work?
--
-
Hi,
On 16/05/2019 17.24, Rudolf J Streif wrote:
> Thank you, Paul. I did read Andrei's excellent documentation and
> enabled I2C and SPI etc.
And it didn't work?
--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan
--
___
yocto mailing
Thank you, Paul. I did read Andrei's excellent documentation and enabled
I2C and SPI etc.
:rjs
On 5/16/19 8:39 AM, Paul Barker wrote:
On Thu, 16 May 2019, at 16:33, Rudolf J Streif wrote:
I am trying to use the "official" RPi 7" touch display
Thank you, Andrei. Much appreciated.
https://pastebin.com/bHUHaRkL
It's the config.txt that is packaged with the image.
:rjs
On 5/16/19 9:01 AM, Andrei Gherzan wrote:
HI,
On 16/05/2019 16.31, Rudolf J Streif wrote:
I am trying to use the "official" RPi 7" touch display
Hi guys,
I'm currently finishing my masters thesis and I really need a bit of
help if possible. The project is entitled "Empowering git repositories
with visualization tools to aid awareness of dependencies in open
source" and I have a questionnaire which I need to get some feedback on
and filled
HI,
On 16/05/2019 16.31, Rudolf J Streif wrote:
> I am trying to use the "official" RPi 7" touch display
> (https://www.raspberrypi.org/products/raspberry-pi-touch-display/)
> with meta-raspberrypi (most recent from master). However, I cannot get
> it to work. As a matter of fact the display does
On 12/05/2019 16.04, Jean-Christian de Rivaz wrote:
> Le 11.05.19 à 21:46, Paul Barker a écrit :
>> On Sat, 11 May 2019, at 20:44, Jean-Christian de Rivaz wrote:
>>> Hi,
>>>
>>> I try to use the Linux 4.19 for the RaspberryPi from the
>>> meta-raspberrypi recipe linux-raspberrypi_4.19.bb but the
On Thu, 16 May 2019, at 16:33, Rudolf J Streif wrote:
> I am trying to use the "official" RPi 7" touch display
> (https://www.raspberrypi.org/products/raspberry-pi-touch-display/) with
> meta-raspberrypi (most recent from master). However, I cannot get it to
> work. As a matter of fact the
Yes, kallsyms is a helper program for handling symbols during kernel build
and is not itself transferred to target.
For the kernel, it is essentially used for the target, but its compilation
process needs native tools like kallsyms. Is this case not be considered in
Yocto at the beginning?
Anyway,
On Wed, May 15, 2019 at 10:57:00AM +, Martin Jansa wrote:
> * it's still used by:
> recipes-devtools/elfutils/elfutils_0.148.bb:LICENSE = "(GPL-2+ &
> Elfutils-Exception)"
> * was removed in oe-core with:
>
>
* it's still used by:
recipes-devtools/elfutils/elfutils_0.148.bb:LICENSE = "(GPL-2+ &
Elfutils-Exception)"
* was removed in oe-core with:
http://git.openembedded.org/openembedded-core/commit/?id=88188807a6ac9bab738a69f6b4caba9ed092d78f
* causing:
do_rootfs: The license listed
I have a use case where I want psplash to write its image to the frame
buffer without supporting a progress bar. That means a single write
into the framebuffer. Then it's done.
This patch adds a PSPLASH_ENABLE_CLIENT config option which defaults
to 1 (i.e. true). This keeps the default behaviour
I have a system where the framebuffer size doesn't match the display
size. In order to figure out which portion of the framebuffer makes it
to the screen I wanted a way to quickly move the picture around. I
decided to add a command line option for a horizontal offset that at
runtime lets you
IrDA support was removed in upstream kernel 4.17,
and irda-utils as well as the feature are now also removed.
Signed-off-by: Adrian Bunk
---
documentation/ref-manual/ref-features.xml | 4
1 file changed, 4 deletions(-)
diff --git a/documentation/ref-manual/ref-features.xml
21 matches
Mail list logo
