lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 25 Jan 2017 14:50:37 +0100
From:   Jean Delvare <>
To:     Sudeep Holla <>
Cc:     LKML <>,
        "Jon Medhurst (Tixy)" <>
Subject: Re: [PATCH] firmware: arm_scpi: Add hardware dependencies

On Wed, 25 Jan 2017 13:38:47 +0000, Sudeep Holla wrote:
> On 25/01/17 13:32, Jean Delvare wrote:
> > With a name like that, I assume that the ARM SCPI protocol is only
> > useful on the ARM architectures.
> > 
> > Signed-off-by: Jean Delvare <>
> > Fixes: 8f1498c03d15 ("firmware: arm_scpi: make it depend on MAILBOX instead of")
> > Cc: Sudeep Holla <>
> > Cc: Jon Medhurst (Tixy) <>
> > ---
> > Please correct me if I'm wrong.
> I won't say you are wrong but the reason why it's named arm_scpi is
> because the protocol was developed by ARM. It doesnn't mean only
> ARM/ARM64 needs to use it, it can be used on any architecture for
> inter-processor communication using any communication technique
> (currently mailbox is the only supported in the driver)

OK, thanks for the clarification. In practice, what other architectures
are using it?

Jean Delvare
SUSE L3 Support

Powered by blists - more mailing lists