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>] [day] [month] [year] [list]
Message-ID: <AANLkTinJeMKBzsBwgSLcHXtexM2oI3S97HO8IPri9EA7@mail.gmail.com>
Date:	Tue, 8 Jun 2010 22:34:33 +0800
From:	Wan ZongShun <mcuos.com@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-rtc <rtc-linux@...glegroups.com>, jeffjway@...il.com
Subject: Fwd: [rtc-linux] RTC_SET_TIME: Inappropriate ioctl for device

CC to LKML to do further discussion.

---------- Forwarded message ----------
From: Wan ZongShun <mcuos.com@...il.com>
Date: 2010/6/8
Subject: Re: [rtc-linux] RTC_SET_TIME: Inappropriate ioctl for device
To: rtc-linux@...glegroups.com, jeffjway@...il.com


Hi Jeff,

2010/6/8 JJeff <jeffjway@...il.com>:
> Whenever I try to run 'hwclock', I get the error:
> "RTC_RD_TIME: Inappropriate ioctl for device:"
> or
> " RTC_SET_TIME: Inappropriate ioctl for device"
> if I run it with the -w option
>

Both of errors indicate your user layer or kernel driver is using a
wrong IOCTL command,
maybe your RTC_RD_TIME of user layer doesnot match the  RTC_RD_TIME of
kernel layer.
so driver return a '--ENOTTY' error no.

The better thing is you can write a rtc test application to identify
your driver works well.

Maybe you can change other version hwclock for testing.

> Is the hwclock too old a version or something?  The option --version
> is not recognised.
>
>
> I'm trying to use the hwclock command to sync the time each bootup, so
> any other ideas as to how to do it would be good too.
>
> Thanks
>
> Jeff
>
> --
> You received this message because you are subscribed to "rtc-linux".
> Membership options at http://groups.google.com/group/rtc-linux .
> Please read http://groups.google.com/group/rtc-linux/web/checklist
> before submitting a driver.



--
*linux-arm-kernel mailing list
mail addr:linux-arm-kernel@...ts.infradead.org
you can subscribe by:
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

* linux-arm-NUC900 mailing list
mail addr:NUC900@...glegroups.com
main web: https://groups.google.com/group/NUC900
you can subscribe it by sending me mail:
mcuos.com@...il.com



-- 
*linux-arm-kernel mailing list
mail addr:linux-arm-kernel@...ts.infradead.org
you can subscribe by:
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

* linux-arm-NUC900 mailing list
mail addr:NUC900@...glegroups.com
main web: https://groups.google.com/group/NUC900
you can subscribe it by sending me mail:
mcuos.com@...il.com
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ