similar to: Optimal Hardware

> They instantly got us to look at the output of zttest and we found that this was (in their words) 'extremely low', with 'best' and > 'worst' readings of 99.975586% and 99.963379% respectively. Might want to give PCI latency setting a try, it helped for me. My ZTTEST would drop occasionally to 99.95% until I set: setpci -v -s 01:01.0 latency_timer=ff

I have an opportunity to pick up a couple of NetFinity 5500's 4 way Xeon 550's w/ 2 gig RAM for very little $$$ I have seen this: http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg00719.html In it, there is a passing remark to the Digium cards having problems with NetFinity's. Can anyone here comment on whether this is still an issue with * 1.0? It'd be a bummer if

On 2020/9/3 ??1:34, Jie Deng wrote: > Add an I2C bus driver for virtio para-virtualization. > > The controller can be emulated by the backend driver in > any device model software by following the virtio protocol. > > This driver communicates with the backend driver through a > virtio I2C message structure which includes following parts: > > - Header: i2c_msg addr,

On Thu, Sep 03, 2020 at 01:34:45PM +0800, Jie Deng wrote: > Add an I2C bus driver for virtio para-virtualization. > > The controller can be emulated by the backend driver in > any device model software by following the virtio protocol. > > This driver communicates with the backend driver through a > virtio I2C message structure which includes following parts: > > -

On 2020/9/11 ??11:48, Jie Deng wrote: > Add an I2C bus driver for virtio para-virtualization. > > The controller can be emulated by the backend driver in > any device model software by following the virtio protocol. > > This driver communicates with the backend driver through a > virtio I2C message structure which includes following parts: > > - Header: i2c_msg addr,

On 2020/9/3 ??1:34, Jie Deng wrote: > Add an I2C bus driver for virtio para-virtualization. > > The controller can be emulated by the backend driver in > any device model software by following the virtio protocol. > > This driver communicates with the backend driver through a > virtio I2C message structure which includes following parts: > > - Header: i2c_msg addr,

Hi, I''m starting a new application, and want it to be tested out the wazoo. Do people duplicate tests in both unit and functional tests? Say I have a Product model. I write tests that make sure that it acts appropriately (tests the validations and so forth). Is it good practice to also write the functional tests for the same sort of tests (i.e. make sure that the validations are

On Tue, Sep 22, 2020 at 10:58:43AM +0800, Jie Deng wrote: > Add an I2C bus driver for virtio para-virtualization. > > The controller can be emulated by the backend driver in > any device model software by following the virtio protocol. > > This driver communicates with the backend driver through a > virtio I2C message structure which includes following parts: > > -

Add an I2C bus driver for virtio para-virtualization. The controller can be emulated by the backend driver in any device model software by following the virtio protocol. This driver communicates with the backend driver through a virtio I2C message structure which includes following parts: - Header: i2c_msg addr, flags, len. - Data buffer: the pointer to the I2C msg data. - Status: the

Add an I2C bus driver for virtio para-virtualization. The controller can be emulated by the backend driver in any device model software by following the virtio protocol. This driver communicates with the backend driver through a virtio I2C message structure which includes following parts: - Header: i2c_msg addr, flags, len. - Data buffer: the pointer to the I2C msg data. - Status: the

It turns out that while disabling i2c bus access from software when the GPU is suspended was a step in the right direction with: commit 342406e4fbba ("drm/nouveau/i2c: Disable i2c bus access after ->fini()") We also ended up accidentally breaking the vbios init scripts on some older Tesla GPUs, as apparently said scripts can actually use the i2c bus. Since these scripts are executed

Hi, it happens I could get a Netfinity 5100 IBM server and I was wondering if anyone has successfully installed CentOS4 (or even 3) on this server. Thanks, have a nice day Simone

Add an I2C bus driver for virtio para-virtualization. The controller can be emulated by the backend driver in any device model software by following the virtio protocol. This driver communicates with the backend driver through a virtio I2C message structure which includes following parts: - Header: i2c_msg addr, flags, len. - Data buffer: the pointer to the I2C msg data. - Status: the

Add an I2C bus driver for virtio para-virtualization. The controller can be emulated by the backend driver in any device model software by following the virtio protocol. This driver communicates with the backend driver through a virtio I2C message structure which includes following parts: - Header: i2c_msg addr, flags, len. - Data buffer: the pointer to the I2C msg data. - Status: the

Hello everyone, This set will switch the users of pm_runtime_put_autosuspend() to __pm_runtime_put_autosuspend() while the former will soon be re-purposed to include a call to pm_runtime_mark_last_busy(). The two are almost always used together, apart from bugs which are likely common. Going forward, most new users should be using pm_runtime_put_autosuspend(). Once this conversion is done and

Hello! I just wanted to tell everyone that I have successfully used a TDM400 with an IBM Netfinity 5600 server. I used PCI Slot 3 (the first hot-swap PCI slot). I had a ServeRAID 3L controller in slot 1as well, which managed the server's array. Other than that, there was nothing extra installed. 2x667MHz PIII, 1GB RAM, 4 x 18GB hot-swap SCSI drives. The only problems I had were Ouch

I hope the CentOS people don't mind me cross-posting for their input. I've just done a clean, text-mode minimal WBEL4 install on an IBM Netfinity 4500, essentially the same hardware as an xSeries 340. The install went fine but now the box will boot, run through the initrd init sequence, perform its switchroot then hang here... SELinux: Initializing. SELinux: Starting in permissive mode

On 9/10/20 8:48 PM, Jie Deng wrote: > diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig > index 293e7a0..70c8e30 100644 > --- a/drivers/i2c/busses/Kconfig > +++ b/drivers/i2c/busses/Kconfig > @@ -21,6 +21,17 @@ config I2C_ALI1535 > This driver can also be built as a module. If so, the module > will be called i2c-ali1535. > > +config

I was browsing the applications developed in zaptel and came across zttest. After I run it, I get the following: Opened pseudo zap interface, measuring accuracy... 99.975586% 99.987793% 99.987793% 99.987793% 99.987793% 100.000000% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.975586% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793%

Add an I2C bus driver for virtio para-virtualization. The controller can be emulated by the backend driver in any device model software by following the virtio protocol. This driver communicates with the backend driver through a virtio I2C message structure which includes following parts: - Header: i2c_msg addr, flags, len. - Data buffer: the pointer to the i2c msg data. - Status: the