linux-kernel - Re: [PATCH 0/2][RFC] Try to handle hctosys w/ rtc modules

lists.openwall.net		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 linux-cve-announce 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]

Message-ID: <20140630213716.36dd4227@linux.lan.towertech.it>
Date:	Mon, 30 Jun 2014 21:37:16 +0200
From:	Alessandro Zummo <a.zummo@...ertech.it>
To:	Marc Dietrich <marvin24@....de>
Cc:	Alexander Holler <holler@...oftware.de>,
	John Stultz <john.stultz@...aro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	John Whitmore <arigead@...il.com>
Subject: Re: [PATCH 0/2][RFC] Try to handle hctosys w/ rtc modules

On Sat, 28 Jun 2014 20:54:33 +0200
Marc Dietrich <marvin24@....de> wrote:

> > Besides that the current hctosys-mechanism doesn't really work with 
> > hot-plugable devices at all. Guess what N will be when you unplug and 
> > plug in such a RTC again.  
> 
> We have a patch in the kernel which binds the rtc number to the
> hw device, so this even works for hotpluggable devices (at least on
> systems supporting device-tree). Not sure what your needs are.

 I'm still not sure about how to solve this, maybe it would be better to
 identify the hctosys device that should be used at boot with 
 a different identifier than rtcX (and move the option to the kernel command line)

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/