domo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Hello EveryBody,
I have a COMPAQ ML570 (2xPIII-700Mhz/1MBytes Cache, 2 x NCR SCSI controller,
1 SMART ARRAY 5304 (128 MBytes Cache). I test with linux 2.4.2-ac20, and all
disks, CPU&#
Hi Dave,
Am Freitag, dem 13.09.2024 um 18:40 +0100 schrieb Dave Stevenson:
> On Thu, 12 Sept 2024 at 15:51, Dave Stevenson
> wrote:
> >
> > Hi André & Ricardo
> >
> > On Thu, 12 Sept 2024 at 14:41, Ricardo Ribalda Delgado
> > wrote:
> > >
>
Hi Ricardo,
Am Donnerstag, dem 12.09.2024 um 15:40 +0200 schrieb Ricardo Ribalda
Delgado:
> On Mon, Sep 2, 2024 at 11:54 PM André Apitzsch via B4 Relay
> wrote:
> >
> > From: André Apitzsch
> >
> > Remove format and crop settings from register sequences and set
I needed this when compiling for pandaboard at commit:
0944c0a03465718909ba8e800a5230528aeabafb
Signed-off-by: André Hentschel From:
=?UTF-8?q?Andr=C3=A9=20Hentschel?=
From: =?UTF-8?q?Andr=C3=A9=20Hentschel?=
Date: Wed, 6 Feb 2013 23:16:20 +0100
Subject: [PATCH] arm: Include soc.h to fix
could only test it with kernel 3.4.6
Signed-off-by: André Hentschel
From: =?UTF-8?q?Andr=C3=A9=20Hentschel?=
Date: Wed, 6 Feb 2013 23:24:54 +0100
Subject: [PATCH] arm: Preserve TPIDRURW on context switch
---
arch/arm/include/asm/thread_info.h | 1 +
arch/arm/include/asm/tls.h | 43
Am 06.02.2013 23:51, schrieb Russell King - ARM Linux:
> On Wed, Feb 06, 2013 at 11:43:10PM +0100, André Hentschel wrote:
>> There are more and more applications coming to WinRT, Wine could support
>> them,
>> but mostly they expect to have the thread environment block
Am 08.02.2013 16:48, schrieb Will Deacon:
> On Wed, Feb 06, 2013 at 11:01:23PM +0000, André Hentschel wrote:
>> Am 06.02.2013 23:51, schrieb Russell King - ARM Linux:
>>> On Wed, Feb 06, 2013 at 11:43:10PM +0100, André Hentschel wrote:
>>>> There are more and mor
Am 08.02.2013 16:48, schrieb Will Deacon:
> On Wed, Feb 06, 2013 at 11:01:23PM +0000, André Hentschel wrote:
>> Am 06.02.2013 23:51, schrieb Russell King - ARM Linux:
>>> On Wed, Feb 06, 2013 at 11:43:10PM +0100, André Hentschel wrote:
>>>> There are more and mor
Am 12.02.2013 15:09, schrieb Will Deacon:
> Hi Andre,
>
> On Tue, Feb 12, 2013 at 02:02:59PM +0000, André Hentschel wrote:
>> Am 08.02.2013 16:48, schrieb Will Deacon:
>>> On Wed, Feb 06, 2013 at 11:01:23PM +, André Hentschel wrote:
>>>> No, i'm n
Am 12.02.2013 16:02, schrieb Matthieu CASTET:
> Will Deacon a écrit :
>> Hi Andre,
>>
>> On Tue, Feb 12, 2013 at 02:02:59PM +, André Hentschel wrote:
>>> Am 08.02.2013 16:48, schrieb Will Deacon:
>>>> On Wed, Feb 06, 2013 at 11:01:23PM +, André H
Am 15.08.2013 20:27, schrieb André Hentschel:
> Hi Jonathan,
>
> Am 15.08.2013 19:29, schrieb Jonathan Austin:
>> Hi André
>> What I've *not* tested:
>> * As this CPU does not have the tls register, I haven't run any tests that
>> try to read/write it,
From: =?UTF-8?q?Andr=C3=A9=20Hentschel?=
There are more and more applications coming to WinRT, Wine could support them,
but mostly they expect to have the thread environment block (TEB) in TPIDRURW.
This register must be preserved per thread instead of being cleared.
Signed-off-by: André
Am 22.04.2013 17:18, schrieb Will Deacon:
> On Mon, Apr 22, 2013 at 03:36:16PM +0100, Russell King - ARM Linux wrote:
>> On Fri, Apr 19, 2013 at 05:54:35PM +0200, André Hentschel wrote:
>>> From: =?UTF-8?q?Andr=C3=A9=20Hentschel?=
>>>
>>> There are more and mor
From: André Hentschel
Since commit 6a1c53124aa1 the user writeable TLS register was zeroed to
prevent it from being used as a covert channel between two tasks.
There are more and more applications coming to Windows RT,
Wine could support them, but mostly they expect to have
the thread
On 18.06.2013 12:07, Will Deacon wrote:
> On Mon, Jun 17, 2013 at 11:13:48PM +0100, André Hentschel wrote:
>> From: André Hentschel
>>
>> Since commit 6a1c53124aa1 the user writeable TLS register was zeroed to
>> prevent it from being used as a covert channel between
From: André Hentschel
Since commit 6a1c53124aa1 the user writeable TLS register was zeroed to
prevent it from being used as a covert channel between two tasks.
There are more and more applications coming to Windows RT,
Wine could support them, but mostly they expect to have
the thread
Hi Jonathan,
Any updates on this?
Am 17.07.2013 21:49, schrieb André Hentschel:
> Am 17.07.2013 13:10, schrieb Jonathan Austin:
>> Hi André,
>> Do you have access to anything v6-NOT-k-ish? If not I can try and test this
>> on something appropriate. How does your test-case a
Am 14.08.2013 18:20, schrieb Jonathan Austin:
> Hi André,
>
> On 14/08/13 15:07, André Hentschel wrote:
>> Hi Jonathan,
>> Any updates on this?
>>
>
> I was holding out to see the version with ldrd at the top, as discussed below
> - I never saw a version wit
Hi Jonathan,
Am 15.08.2013 19:29, schrieb Jonathan Austin:
> Hi André
>
> (I've put RMK and LAKML back on Cc: they got dropped somewhere along the way)
>
> On 14/08/13 22:21, André Hentschel wrote:
>>>>>> [...]
>>>>>>>> Now
From: André Hentschel
This patch intents to reduce loading instructions when the resulting value is
not used.
It's a follow up on a4780adeefd042482f624f5e0d577bf9cdcbb760
Signed-off-by: André Hentschel
---
This patch is against Linux 3.11-rc1 (ad81f0545ef01ea651886dddac4bef6cec9
Hi Jonathan,
First, thank you for your review.
Am 16.07.2013 19:31, schrieb Jonathan Austin:
> Hi André,
>
> On 15/07/13 18:14, André Hentschel wrote:
>> From: André Hentschel
>>
>> This patch intents to reduce loading instructions when the resulting value
>>
Am 17.07.2013 13:10, schrieb Jonathan Austin:
> Hi André,
>
> On 16/07/13 20:27, André Hentschel wrote:
>> Hi Jonathan, First, thank you for your review.
>>
>> Am 16.07.2013 19:31, schrieb Jonathan Austin:
>>> Hi André,
>>>
>>> On 15/07/13 18
Am 24.04.2013 11:42, schrieb Will Deacon:
> Hi Andrew,
>
> On Tue, Apr 23, 2013 at 11:42:22PM +0100, André Hentschel wrote:
>> Am 23.04.2013 11:15, schrieb Will Deacon:
>>> You could introduce `get' tls functions, which don't do anything for CPUs
>>> wit
Am 03.05.2013 17:24, schrieb Jonathan Austin:
> Hi Russell,
>
> Thanks for the comments - you're right about the 'switch_tls'
> being more appropriate - needed to take a step back to see that.
>
> I've got a few questions, added inline.
>
> André, Ass
mp1, tmp2
>
> How do you feel about calling tp and trw something different? tpidro
> and tpidrw, or tp and tpuser?
>
> The naming threw me off slightly first time I read this new signature
> (tp=thread_pointer/tls_pointer/etc).
>
FWIW i think tp&tpuser is more consistent.
&
must always read
TPIDRURW in copy_thread.
Signed-off-by: André Hentschel
Signed-off-by: Will Deacon
Signed-off-by: Jonathan Austin
---
This patch is against a86d52667d8eda5de39393ce737794403bdce1eb
I could only test it with kernel 3.4.6, beside using Wine for testing i also
used https
Hi Will,
thx for having a look.
Am 08.05.2013 10:57, schrieb Will Deacon:> Hi Andre,
>
> On Tue, May 07, 2013 at 09:51:00PM +0100, André Hentschel wrote:
>> From: =?UTF-8?q?Andr=C3=A9=20Hentschel?=
>
> Might just be my mailer, but you should check that your name is intact
must always read
TPIDRURW in copy_thread.
Signed-off-by: André Hentschel
Signed-off-by: Will Deacon
Signed-off-by: Jonathan Austin
---
This patch is against a86d52667d8eda5de39393ce737794403bdce1eb
Why so much Signed-off-bys? Some History:
The first patch had performance issues pointed out
Am 23.04.2013 11:15, schrieb Will Deacon:
> On Mon, Apr 22, 2013 at 10:07:35PM +0100, André Hentschel wrote:
>> Am 22.04.2013 17:18, schrieb Will Deacon:
>>> On Mon, Apr 22, 2013 at 03:36:16PM +0100, Russell King - ARM Linux wrote:
>>>> On Fri, Apr 19, 2013 at 05:
Am 08.05.2013 21:03, schrieb André Hentschel:
> From: =?UTF-8?q?Andr=C3=A9=20Hentschel?=
>
> Since commit 6a1c53124aa1 the user writeable TLS register was zeroed to
> prevent it from being used as a covert channel between two tasks.
>
> There are more and more applications com
Am 20.05.2013 13:03, schrieb Jonathan Austin:
> Hi André
>
> On 18/05/13 16:02, André Hentschel wrote:
>> Am 08.05.2013 21:03, schrieb André Hentschel:
>>> From: =?UTF-8?q?Andr=C3=A9=20Hentschel?=
>>>
>
> This is strangely formatted for me too, and I use
From: André Hentschel
Since commit 6a1c53124aa1 the user writeable TLS register was zeroed to
prevent it from being used as a covert channel between two tasks.
There are more and more applications coming to Windows RT,
Wine could support them, but mostly they expect to have
the thread
On Mon, 14 Jan 2013 18:08:45 +0100
Stefan Bader wrote:
> On 14.01.2013 17:34, Borislav Petkov wrote:
> > On Mon, Jan 14, 2013 at 04:58:54PM +0100, Stefan Bader wrote:
> >> Starting with kernel v3.7 the following commit added a quirk
> >> to obtain the real frequencies of certain AMD systems:
> >>
Dawson Engler <[EMAIL PROTECTED]> wrote:
> enclosed are three bugs found in the 2.4.1 kernel by an extension
Why are you guys running these tests against an already old kernel?
I would suggest running it against at least Linus' latest version, or
preferably Alan's -ac tree.
-
ou basically wanted 2.4.1 to be "boring".
I guess it's the "pushover and wimp" showing his face again:-)
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
inserted in and removed from the running kernel whenever you want),
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
if you have an Intel I810 graphics card. If M is
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Adrian Nims
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
--
:::
ICQ: 75132336
http://www.aphroland.org/
http://www.linuxpowered.net/
[EMAIL PROTECTED]
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/nul
On Mon, Sep 11, 2000 at 09:11:59AM +0200, Andreas Jaeger wrote:
> -echo "*** Next, you may run 'make zImage', 'make zdisk', or 'make zlilo'."
> +echo "*** Next, you may run 'make bzImage', 'make bzdisk', or 'make
x
Code; c012c1cf
11: 85 d2 test %edx,%edx
Code; c012c1d1
13: 74 00 je 15 <_EIP+0x15> c012c1d3
Aiee, killing interrupt handler
Kernel panic: Attempted to kill the idle task!
--
// André
-
To unsubscribe from this list: send the line "unsubscrib
st reading e-mail in Mutt. I had to type the oops down by hand,
but I will provide ksymoops output soon if you need it.
--
// André
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
in response to tcp connections with ECN
bits set
Product: PIX
Component: fw
Severity: 2Status: R [Resolved]
Version Found: 5.1(1) Fixed-in Version: 5.1(2.206) 5.1(2.207)
5.2(1.200)
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe
icense" (ignoring case) was missed.
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Oct 17, 2000 at 05:50:18AM -0400, Mike A. Harris wrote:
> So Linus's COPYING file in the source root is correct, and the
> other two files can be deleted.
Just make sure that no document points to these two files.
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscri
check failed for 'diva.c'
md5sum: MD5 check failed for 'sedlbauer.c'
They all seam to be related to the ISDN code. Is this
something to worry about?
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&q
ng ("vs-: reiserfs_rename: could not cut old name. Fsck
+later?\n");
old_dir->i_size -= DEH_SIZE + old_de.de_entrylen;
old_dir->i_blocks = ((old_dir->i_size + 511) >> 9);
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the
init_rwsem(struct rw_semaphore *sem)
{
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
is held, which guarantees existence of swap device.
*
* Note: if swap_map[] reaches SWAP_MAP_MAX the entries are treated as
* "permanent", but will be reclaimed by the next swapoff.
diff -ur linux-2.4.1-ac4/net/core/dev.c linux/net/core/dev.c
--- linux-2.4.1-ac4/net/core/dev.c Wed Feb
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Was the TODO list at http://linux24.sourceforge.net just meant to be useful
> before 2.4.0 was released?
It would be interesting to know how many of these issues have been fixed by
now.
--
André Dahlqvist <[EMAIL PROTECTED]>
-
T
Marcelo Tosatti <[EMAIL PROTECTED]> wrote:
> It did not fixed any interactivity problem.
I agree. Kernels after 2.4.4 uses a *lot* more swap for me, which I guess
might be part of the reason for the slowdown.
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this
André Dahlqvist <[EMAIL PROTECTED]> wrote:
> I agree. Kernels after 2.4.4 uses a *lot* more swap for me, which I guess
> might be part of the reason for the slowdown.
Following up on myself, here are some numbers:
Freshly booted 2.4.4 with X and Mozilla running, 'f
a lot slower.
Let me know if you want me to do more tests.
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Al Boldi wrote:
Bartlomiej Zolnierkiewicz wrote: {
On 7/4/05, Al Boldi <[EMAIL PROTECTED]> wrote:
Hdparm -tT gives 38mb/s in 2.4.31
Cat /dev/hda > /dev/null gives 2% user 33% sys 65% idle
Hdparm -tT gives 28mb/s in 2.6.12
Cat /dev/hda > /dev/null gives 2% user 25% sys 0% idle 73% IOWAIT
The
Martin Wilck wrote:
Jens Axboe wrote:
If I am reading the specs correctly, that'd mean the ahci driver is
wrong in setting the SActive bit.
I completely agree, that was my reading of the spec as well and hence my
original posts about this in the NCQ thread.
Have you (or has anybody else)
. The
kernel didn't oops, and I actually had to run several kernel compiles at
the same time to have gcc die.
Try memtest86 on the suspect box.
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
's up with the realtek driver update I would say.
I'm not on the list so please CC me replys.
Thanks.
----
André Cruz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://
# ld -v
--
André Dahlqvist <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi Maxime,
On 26/07/16 21:30, Maxime Ripard wrote:
> Hi,
>
> Here is the previous A64 patches made by Andre [1], reworked to use
> the new sunxi-ng clock framework.
>
> This uses the current H3 clock code, as both are really similar. The
> first patches are just meant to rework slightly the H3 c
On 09/09/16 21:10, Maxime Ripard wrote:
Hi Maxime,
> From: Andre Przywara
>
> The Allwinner A64 SoC is a low-cost chip with 4 ARM Cortex-A53 cores
> and the typical tablet / TV box peripherals.
> The SoC is based on the (32-bit) Allwinner H3 chip, sharing most of
> the peripherals and the memor
Hi Maxime,
thanks for your answer, much appreciated!
On 23/08/16 20:31, Maxime Ripard wrote:
> Hi Andre,
>
> On Mon, Aug 01, 2016 at 02:43:06AM +0100, André Przywara wrote:
>> Hi Maxime,
>>
>> On 26/07/16 21:30, Maxime Ripard wrote:
>>> Hi,
>>>
>&
t about the location of the symbol, we
can make lx-dmesg work again. While at it, do the same
for the other symbols we need from printk.c
Signed-off-by: André Draszik
---
scripts/gdb/linux/dmesg.py | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/scripts/gdb/l
buf
$3 = (char **) 0x8120fe40
(gdb) p &'verifier.c'::log_buf
$4 = (char **) 0x8120fe40
(gdb) p &'printk.c'::log_buf
$5 = (char **) 0x8048b7d0
By being explicit about the location of the symbol, we
can make lx-dmesg work again. While at it, do the same
for t
buf
$3 = (char **) 0x8120fe40
(gdb) p &'verifier.c'::log_buf
$4 = (char **) 0x8120fe40
(gdb) p &'printk.c'::log_buf
$5 = (char **) 0x8048b7d0
By being explicit about the location of the symbol, we
can make lx-dmesg work again. While at it, do the same
for t
On 12/05/17 18:14, Tony Lindgren wrote:
> * Tony Lindgren [170512 08:39]:
>> * Linus Walleij [170512 02:28]:
>>> On Thu, May 11, 2017 at 4:20 PM, Andre Przywara
>>> wrote:
Linus, can you shed some light if this array creation serves some purpose?
>>>
>>> Tony [author of this function] can
exactly
that use-case.
Given the watchdog driver core doesn't know what timeout was
originally set by whoever started the watchdog (boot loader),
we make sure to update the timeout in the hardware according
to what the watchdog core thinks it is.
Signed-off-by: André Draszik
Cc: Wim Van Sebroec
This does the necessary cleanup on driver unload automatically.
Signed-off-by: André Draszik
Reviewed-by: Guenter Roeck
Cc: Wim Van Sebroeck
Cc: Guenter Roeck
Cc: linux-watch...@vger.kernel.org
Cc: John Crispin
---
Changes in v2:
- add reviewed-by
---
drivers/watchdog/mt7621_wdt.c | 13
Thank you Ted,
On Wed, 2018-01-17 at 13:05 -0500, Theodore Ts'o wrote:
> On Wed, Jan 17, 2018 at 02:38:59PM +0000, André Draszik wrote:
> > > > [...]
> > >
> > > Please be very clear about exactly what security properties are
> > > achieved
> >
We now try to acquire the key according to the
encryption policy from both key types, 'logon'
as well as 'encrypted'.
Signed-off-by: André Draszik
Cc: "Theodore Y. Ts'o"
Cc: Jaegeuk Kim
Cc: linux-fscr...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
C
Signed-off-by: André Draszik
Cc: "Theodore Y. Ts'o"
Cc: Jaegeuk Kim
Cc: Jonathan Corbet
Cc: linux-fscr...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Eric Biggers
Cc: linux-...@vger.kernel.org
---
Documentation/filesystems/fscrypt.rst | 56
Thanks Eric for the review!
On Wed, 2018-01-10 at 20:00 -0800, Eric Biggers wrote:
> Hi André,
>
> On Wed, Jan 10, 2018 at 12:44:16PM +0000, André Draszik wrote:
> > This is heavily based on commit 79a73d188726
> > ("encrypted-keys: add ecryptfs format support"
Hi Eric,
On Wed, 2018-01-10 at 20:48 -0800, Eric Biggers wrote:
> Hi André,
>
> On Wed, Jan 10, 2018 at 12:44:18PM +0000, André Draszik wrote:
> > diff --git a/Documentation/security/keys/fscrypt.rst
> > b/Documentation/security/keys/fscrypt.rst
> > new file mode 10
imply insert them again
(optionally benefitting from the TPM's capability to only
unseal kmk.blob when the system is in the expected state,
thereby also protecting fscrypt.blob):
keyctl add trusted kmk "load $(cat /keys/kmk.blob)" @u
keyctl add encrypted fscrypt:1234567890123456
what timeout was
originally set by whoever started the watchdog (boot loader),
we make sure to update the timeout in the hardware according
to what the watchdog core thinks it is.
Signed-off-by: André Draszik
Cc: Wim Van Sebroeck
Cc: Guenter Roeck
Cc: linux-watch...@vger.kernel.org
Cc: John Cr
This does the necessary cleanup on driver unload automatically.
Signed-off-by: André Draszik
Cc: Wim Van Sebroeck
Cc: Guenter Roeck
Cc: linux-watch...@vger.kernel.org
Cc: John Crispin
---
drivers/watchdog/mt7621_wdt.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff
details about the usage of encrypted keys with the fscrypt
subsystem can be found in the file 'Documentation/security/keys/fscrypt.rst'.
Signed-off-by: André Draszik
Cc: Mimi Zohar
Cc: David Howells
Cc: James Morris
Cc: "Serge E. Hallyn"
Cc: "Theodore Y. Ts'o
We now try to acquire the key according to the
encryption policy from both key types, 'logon'
as well as 'encrypted'.
Signed-off-by: André Draszik
Cc: Mimi Zohar
Cc: David Howells
Cc: James Morris
Cc: "Serge E. Hallyn"
Cc: "Theodore Y. Ts'o"
Cc:
Signed-off-by: André Draszik
Cc: Mimi Zohar
Cc: David Howells
Cc: James Morris
Cc: "Serge E. Hallyn"
Cc: "Theodore Y. Ts'o"
Cc: Jaegeuk Kim
Cc: Jonathan Corbet
Cc: Kees Cook
Cc: linux-integr...@vger.kernel.org
Cc: keyri...@vger.kernel.org
Cc: linux-security-
On 12/03/18 16:10, Harald Geyer wrote:
> Add the proper pin group node to reference in board files.
>
> Signed-off-by: Harald Geyer
That looks correct to me, so:
Reviewed-by: Andre Przywara
But out of curiosity, what is this used for? In patch 5/5 I see it being
used, but without a clue for w
On 12/03/18 16:10, Harald Geyer wrote:
Hi,
> Add a watchdog node for the A64, automatically enabled on all boards.
> Tested on Olimex Teres I.
>
> Signed-off-by: Harald Geyer
> ---
> arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/a
On 05/11/2018 03:27 AM, Samuel Holland wrote:
> The Allwinner A64 SoC is known [1] to have an unstable architectural
> timer, which manifests itself most obviously in the time jumping forward
> a multiple of 95 years [2][3]. This coincides with 2^56 cycles at a
> timer frequency of 24 MHz, implying
Hi Lee Jones,
Am Donnerstag, dem 28.09.2023 um 15:42 +0100 schrieb Lee Jones:
> On Sat, 23 Sep 2023, André Apitzsch wrote:
>
> > This commit adds support for Kinetic KTD2026/7 RGB/White LED
> > driver.
> >
> > Signed-off-by: André Apitzsch
> > ---
> &
Add the binding description and the corresponding driver for
the Kinetic KTD2026 and KTD2027.
Signed-off-by: André Apitzsch
---
Changes in v5:
- Restructure brightness_set() + add comments to it to be easier understandable
- Add some line breaks + remove little line-wraps to improve readability
Document Kinetic KTD2026/2027 LED driver devicetree bindings.
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: André Apitzsch
---
.../devicetree/bindings/leds/kinetic,ktd202x.yaml | 171 +
1 file changed, 171 insertions(+)
diff --git a/Documentation/devicetree/bindings
This commit adds support for Kinetic KTD2026/7 RGB/White LED driver.
Signed-off-by: André Apitzsch
---
drivers/leds/rgb/Kconfig| 13 +
drivers/leds/rgb/Makefile | 1 +
drivers/leds/rgb/leds-ktd202x.c | 619
3 files changed, 633
Hi Christophe,
Am Sonntag, dem 01.10.2023 um 17:15 +0200 schrieb Christophe JAILLET:
> Le 01/10/2023 à 15:52, André Apitzsch a écrit :
> > This commit adds support for Kinetic KTD2026/7 RGB/White LED
> > driver.
> >
> > Signed-off-by: André Apitzsch
>
Am Sonntag, dem 01.10.2023 um 22:46 +0200 schrieb Christophe JAILLET:
> Le 01/10/2023 à 18:56, André Apitzsch a écrit :
> > Hi Christophe,
> >
> > Am Sonntag, dem 01.10.2023 um 17:15 +0200 schrieb Christophe
> > JAILLET:
> > > Le 01/10/2023 à 15:52, André Ap
Add the binding description and the corresponding driver for
the Kinetic KTD2026 and KTD2027.
Signed-off-by: André Apitzsch
---
Changes in v6:
- Remove un-needed inits
- Narrow scope of variables
- Release of_node references on early exit
- Pass child node to dev_err() in ktd202x_setup_led_rgb
Document Kinetic KTD2026/2027 LED driver devicetree bindings.
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: André Apitzsch
---
.../devicetree/bindings/leds/kinetic,ktd202x.yaml | 171 +
1 file changed, 171 insertions(+)
diff --git a/Documentation/devicetree/bindings
This commit adds support for Kinetic KTD2026/7 RGB/White LED driver.
Signed-off-by: André Apitzsch
---
drivers/leds/rgb/Kconfig| 13 +
drivers/leds/rgb/Makefile | 1 +
drivers/leds/rgb/leds-ktd202x.c | 625
3 files changed, 639
With the driver for ktd2026 recently applied to linux-leds[1], the LED
can be enabled on longcheer l8910 and l9100.
[1] https://lore.kernel.org/all/20231002-ktd202x-v6-0-26be8eefe...@apitzsch.eu/
Signed-off-by: André Apitzsch
---
André Apitzsch (2):
arm64: dts: qcom: msm8916-longcheer
l8910 uses KTD2026 LED driver. Add it to the device tree.
Tested-by: Stephan Gerhold
Signed-off-by: André Apitzsch
---
.../boot/dts/qcom/msm8916-longcheer-l8910.dts | 51 ++
1 file changed, 51 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8916-longcheer-l8910
l9100 uses KTD2026 LED driver. Add it to the device tree.
Signed-off-by: André Apitzsch
---
.../boot/dts/qcom/msm8939-longcheer-l9100.dts | 51 ++
1 file changed, 51 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8939-longcheer-l9100.dts
b/arch/arm64/boot/dts
Consider an object near to the sensor when their distance is about 4 cm
or below.
Signed-off-by: André Apitzsch
---
arch/arm64/boot/dts/qcom/msm8939-longcheer-l9100.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8939-longcheer-l9100.dts
b/arch/arm64/boot
Am Dienstag, dem 17.10.2023 um 18:25 +0200 schrieb Konrad Dybcio:
>
>
> On 10/16/23 22:18, André Apitzsch wrote:
> > Consider an object near to the sensor when their distance is about
> > 4 cm
> > or below.
> >
> > Signed-off-by: André Apitzsch
> >
Am Mittwoch, dem 18.10.2023 um 10:32 +0200 schrieb Konrad Dybcio:
>
>
> On 10/17/23 22:03, André Apitzsch wrote:
> > Am Dienstag, dem 17.10.2023 um 18:25 +0200 schrieb Konrad Dybcio:
> > >
> > >
> > > On 10/16/23 22:18, André Apitzsch wrote:
> >
Consider an object near to the sensor when their distance is about 4 cm
or below.
Reviewed-by: Konrad Dybcio
Signed-off-by: André Apitzsch
---
Changes in v2:
- add R-b
- Link to v1:
https://lore.kernel.org/r/20231016-bqm5_prox-v1-1-2acdc732b...@apitzsch.eu
---
arch/arm64/boot/dts/qcom/msm8939
Document the compatible for the MSM8926-based Motorola Moto G 4G smartphone.
Signed-off-by: André Apitzsch
---
Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml
b/Documentation/devicetree/bindings
This dts adds support for Motorola Moto G 4G released in 2013.
Add a device tree with initial support for:
- GPIO keys
- Hall sensor
- SDHCI
- Vibrator
Signed-off-by: André Apitzsch
---
André Apitzsch (2):
dt-bindings: arm: qcom: Add Motorola Moto G 4G
ARM: dts: qcom: msm8926
Am Mittwoch, dem 13.12.2023 um 21:44 +0100 schrieb Konrad Dybcio:
>
>
> On 12/13/23 21:33, André Apitzsch wrote:
> > This dts adds support for Motorola Moto G 4G released in 2013.
> I have a similar one in my drawer.. not the 4g kind, titan IIRC?
> Wasn't this one c
This dts adds support for Motorola Moto G 4G released in 2013.
Add a device tree with initial support for:
- GPIO keys
- Hall sensor
- SDHCI
- Vibrator
Signed-off-by: André Apitzsch
---
Changes in v2:
- Make clear it's about Moto G 4G released in 2013.
- Add a-b to patch 1/2.
- Combine
1 - 100 of 725 matches
Mail list logo
