Am 01.10.2017 um 08:01 schrieb Evgeniy Polyakov:
> Hi Jan, Greg
>
> Have you resolved issues with the patch (touch bit export and driver itself)?
> This driver lives outside the kernel quite for a while, do you need any help
> to resolve this?
>
I hope so. I've set up 4.14-rc1, changed my patche
Am 18.09.2017 um 16:19 schrieb GregKH:
> On Mon, Sep 18, 2017 at 03:03:45PM +0200, Jan Kandziora wrote:
>> The w1_ds28e17 driver from the next part of this patch needs to emit
>> single-bit read timeslots to the DS28E17. The w1 subsystem already
>> has this function but it is
exported symbols in drivers/w1/w1_io.c
May be also useful later for writing drivers for other Onewire chips
which do single-bit communication.
Signed-off-by: Jan Kandziora
Acked-by: Evgeniy Polyakov
---
Changes in v5 against v4 in this subpatch:
- adapted to linux-4.14-rc1
Changes in v4 against v3
This subpatch adds a driver for the DS28E17 Onewire to I2C master bridge.
Signed-off-by: Jan Kandziora
Acked-by: Evgeniy Polyakov
---
Changes in v5 against v4 in this subpatch:
- adapted to linux-4.14-rc1
Changes in v4 against v3 in this subpatch:
- adapted to linux-4.12.0
Changes in v3
Am 18.09.2017 um 16:19 schrieb GregKH:
> On Mon, Sep 18, 2017 at 03:03:45PM +0200, Jan Kandziora wrote:
>> The w1_ds28e17 driver from the next part of this patch needs to emit
>> single-bit read timeslots to the DS28E17. The w1 subsystem already
>> has this function but it is
Am 18.09.2017 um 12:57 schrieb GregKH:
> On Tue, Sep 05, 2017 at 04:19:48PM +0300, Evgeniy Polyakov wrote:
>> Hi Jan, Greg
>>
>> 19.07.2017, 23:14, "Jan Kandziora" :
>>> This subpatch adds a driver for the DS28E17 Onewire to I2C master bridge.
>>
This subpatch adds a driver for the DS28E17 Onewire to I2C master bridge.
Signed-off-by: Jan Kandziora
---
Changes in v4 against v3 in this subpatch:
- adapted to linux-4.12.0
Changes in v3 against v2 in this subpatch:
- fixed a bug in using the i2c_adapter_quirks structure
Changes in v2
exported symbols in drivers/w1/w1_io.c
May be also useful later for writing drivers for other Onewire chips
which do single-bit communication.
Signed-off-by: Jan Kandziora
---
Changes in v4 against v3 in this subpatch:
- adapted to linux-4.12.0
No changes in v3 against v2,v1 in this subpatch
exported symbols in drivers/w1/w1_io.c
May be also useful later for writing drivers for other Onewire chips
which do single-bit communication.
Signed-off-by: Jan Kandziora
---
Changes in v4 against v3 in this subpatch:
- adapted to linux-4.12.0
No changes in v3 against v2,v1 in this subpatch
This subpatch adds a driver for the DS28E17 Onewire to I2C master bridge.
Signed-off-by: Jan Kandziora
---
Changes in v4 against v3 in this subpatch:
- adapted to linux-4.12.0
Changes in v3 against v2 in this subpatch:
- fixed a bug in using the i2c_adapter_quirks structure
Changes in v2
Am 17.07.2017 um 16:47 schrieb Greg Kroah-Hartman:
>
> This is in no format that I can apply, sorry.
>
> Jan, can you resend it in a correct format?
>
I sent part 1/2 again with the line breaks fixed (I hope.)
Part 2/2 was okay?
Kind regards
Jan
outside drivers/w1/w1_io.c
This subpatch exports the w1_touch_bit symbol with EXPORT_SYMBOL_GPL,
same as the other exported symbols in drivers/w1/w1_io.c
May be also useful later for writing drivers for other Onewire chips
which do single-bit communication.
Signed-off-by: Jan Kandziora
outside drivers/w1/w1_io.c
This subpatch exports the w1_touch_bit symbol with EXPORT_SYMBOL_GPL,
same as the other exported symbols in drivers/w1/w1_io.c
May be also useful later for writing drivers for other Onewire chips
which do single-bit communication.
Signed-off-by: Jan Kandziora
of kzalloc()
- i2c speed to be set as 100, 400, 900 instead of 0, 1, 2
- added driver parameter documentation
- added sysfs documentation
- Kconfig fixed
This subpatch adds a driver for the DS28E17 Onewire to I2C master bridge.
Signed-off-by: Jan Kandziora
---
>F
Am 27.09.2016 um 19:25 schrieb Stefan Wahren:
>
>> Noralf Trønnes hat am 27. September 2016 um 13:57
>> geschrieben:
>>
>>
>> i2c2 is connected to the HDMI connector and is controlled by the
>> firmware. Disable it to stay out of harms way.
>
> Until this point the commit message is okay, the re
Am Mittwoch, 27. Juni 2007 15:06 schrieb Maxim Levitsky:
>
> Well, I almost sure that this is not true,
> or maybe you are not using dosemu 1.4.0, and other one behaves differently.
>
> Anyway, if I run dosemu 1.4.0 with that setting and stock freedos
> command.com the cpu usage is well below 5%, a
Am Dienstag, 26. Juni 2007 03:44 schrieb Maxim Levitsky:
>
> Hi.
>
> Try to set $_hogthreshold = (1) in dosemu.conf
>
> This helps a lot for me.
>
This "nice"s the dosemu process -- I already use this setting. However, if no
other process is runnable, dosemu will get again all CPU power, which
d
Am Donnerstag, 21. Juni 2007 20:26 schrieb Jan Engelhardt:
>
> Of course there may be hacks that try to figure out if a DOS window is
> idle, waiting for user input. (Seems like a new invention in Windows 2000
> and up). Since dosemu and all the emulators are not running a genuine
> Microsoft DOS /
Dear all,
I like to use an old DOS/Clipper application through DOSEMU on a Linux
application server in a hotel. It works, but (as usual with DOS), it causes
a processor load of 100% in certain situations, while just waiting for user
interaction.
That's kind of stupid, as power saving is heavily d
19 matches
Mail list logo
