search for: bbbbbbbb

...i'm interested in). However if I disable either account the other account will work perfectly. Am I missing something obvious? Thanks in advance, Ray. Excerpts from sip.conf - [general] 8<---- SNIP! ---->8 Register => 1212121:aaaaaaaa at sipgate.co.uk/1212121 Register => 1313131:bbbbbbbb at sipgate.co.uk/1313131 8<---- SNIP! ---->8 [sipgate] type=friend username=1212121 secret=aaaaaaaa host=sipgate.co.uk fromuser=1212121 fromdomain=sipgate.co.uk nat=yes authuser=1212121 dtmfmode=rfc2833 context=infoline_SG insecure=very canreinvite=no disallow=all allow=alaw [2sipgate2] typ...

...Office 2010 Using inotifywait, I tracked how MS Office file save function works. Basically, when clicking on the "diskette" icon, Office do the following thing: - create a temporary file with the new content (AAAAAAAA.tmp) - rename the original file (text.xls) to a new temporary name (BBBBBBBB.tmp) - rename the first temporary file (AAAAAAAA.tmp) to the original filename (test.xls) - delete the second temporary file (BBBBBBBB.tmp) The above renaming valzer works flawlessy 99.9% of times, but sometime it "hang" at point n.3 - renaming the first temporary file to the original...

Has anybody solved this issue. [ http://rubyforge.org/pipermail/facebooker-talk/2008-April/000552.html ] ? NameError (undefined local variable or method `controller'' for #<LeaveController:0xb7144abc>): /app/controllers/application.rb:24:in `verify_authenticity_token''

...ected connect at tempt from 203.13.163.245, who was trying to reach 's@' the s part i can understand by the @nothing ......?!? my iax.conf looks like this register => aaaaaa:bbbbbbb@proxy.freecall.net.au [alphanet] type=friend username=aaaaaaaa auth=plaintext ; ugh plaintext secret=bbbbbbbb host=proxy.freecall.net.au context=main disallow=all allow=ilbc my extensions.conf looks like this [default] exten => s,1,Answer exten => s,2,Dial(SIP/me,40,tr) also I have the same under [main] aswell anyone got any thoughts on this one its making me nuts Thanks

...compatible: Should be "virtio,pci-iommu" +- reg: PCI address of the IOMMU. As defined in the PCI Bus + Binding reference [1], the reg property is a five-cell + address encoded as (phys.hi phys.mid phys.lo size.hi + size.lo). phys.hi should contain the device's BDF as + 0b00000000 bbbbbbbb dddddfff 00000000. The other cells + should be zero. +- #iommu-cells: Each platform DMA master managed by the IOMMU is assigned + an endpoint ID, described by the "iommus" property [2]. + For virtio-iommu, #iommu-cells must be 1. + +Notes: + +- DMA from the IOMMU device isn't manag...

...compatible: Should be "virtio,pci-iommu" +- reg: PCI address of the IOMMU. As defined in the PCI Bus + Binding reference [1], the reg property is a five-cell + address encoded as (phys.hi phys.mid phys.lo size.hi + size.lo). phys.hi should contain the device's BDF as + 0b00000000 bbbbbbbb dddddfff 00000000. The other cells + should be zero. +- #iommu-cells: Each platform DMA master managed by the IOMMU is assigned + an endpoint ID, described by the "iommus" property [2]. + For virtio-iommu, #iommu-cells must be 1. + +Notes: + +- DMA from the IOMMU device isn't manag...

...$architecture; $drivers{$drivername}{"driverpath"} = $driverpath; $drivers{$drivername}{"datafile"} = $datafile; $drivers{$drivername}{"configfile"} = $configfile; } close RPCCLIENT; $/ = "\n"; open(DRIVERTDB, "strings $DRIVERTDBFILE | grep -v 'BBBBBBBB' |"); $dummy = <DRIVERTDB>; $dummy = <DRIVERTDB>; $dummy = <DRIVERTDB>; while (<DRIVERTDB>) { $line = $_; if ($line =~ /^&/) { $drivername = <DRIVERTDB>; $arch = <DRIVERTDB>; chop $drivername; chop $arch; } else { if ($line =~...

...ot;virtio,pci-iommu" > +- reg: PCI address of the IOMMU. As defined in the PCI Bus > + Binding reference [1], the reg property is a five-cell > + address encoded as (phys.hi phys.mid phys.lo size.hi > + size.lo). phys.hi should contain the device's BDF as > + 0b00000000 bbbbbbbb dddddfff 00000000. The other cells > + should be zero. > +- #iommu-cells: Each platform DMA master managed by the IOMMU is assigned > + an endpoint ID, described by the "iommus" property [2]. > + For virtio-iommu, #iommu-cells must be 1. > + > +Notes: > + > +- D...

Implement the virtio-iommu driver, following specification v0.12 [1]. Since last version [2] we've worked on improving the specification, which resulted in the following changes to the interface: * Remove the EXEC flag. * Add feature bit for the MMIO flag. * Change domain_bits to domain_range. Given that there were small changes to patch 5/7, I removed the review and test tags. Please find

Implement the virtio-iommu driver, following specification v0.8 [1]. Changes since v2 [2]: * Patches 2-4 allow virtio-iommu to use the PCI transport, since QEMU would like to phase out the MMIO transport. This produces a complex topology where the programming interface of the IOMMU could appear lower than the endpoints that it translates. It's not unheard of (e.g. AMD IOMMU), and the

Implement the virtio-iommu driver, following specification v0.8 [1]. Changes since v2 [2]: * Patches 2-4 allow virtio-iommu to use the PCI transport, since QEMU would like to phase out the MMIO transport. This produces a complex topology where the programming interface of the IOMMU could appear lower than the endpoints that it translates. It's not unheard of (e.g. AMD IOMMU), and the

Implement the virtio-iommu driver, following specification v0.9 [1]. Only minor changes since v5 [2]. I fixed issues reported by Michael and added tags from Eric and Bharat. Thanks! You can find Linux driver and kvmtool device on v0.9 branches [3], module and x86 support on virtio-iommu/devel. Also tested with Eric's QEMU device [4]. [1] Virtio-iommu specification v0.9, sources and pdf

Implement the virtio-iommu driver, following specification v0.9 [1]. Only minor changes since v5 [2]. I fixed issues reported by Michael and added tags from Eric and Bharat. Thanks! You can find Linux driver and kvmtool device on v0.9 branches [3], module and x86 support on virtio-iommu/devel. Also tested with Eric's QEMU device [4]. [1] Virtio-iommu specification v0.9, sources and pdf

Implement the virtio-iommu driver, following specification v0.8 [1]. Changes since v3 [2]: * Rebase onto v4.20-rc2. Patch 3 now touches drivers/of/base.c instead of drivers/pci/of.c, since the map_rid() function has moved. * Removed the request timeout, that depended on DEBUG. * Other small fixes addressing comments on v3. You can find Linux driver and kvmtool device on my virtio-iommu/v0.8.1

Implement the virtio-iommu driver, following specification v0.9 [1]. Since v4 [2] I fixed the issues reported by Eric, and added Reviewed-by from Eric and Rob. Thanks! I changed the specification to fix one inconsistency discussed in v4. That the device fills the probe buffer with zeroes is now a "SHOULD" instead of a "MAY", since it's the only way for the driver to know

Implement the virtio-iommu driver, following specification v0.9 [1]. Since v4 [2] I fixed the issues reported by Eric, and added Reviewed-by from Eric and Rob. Thanks! I changed the specification to fix one inconsistency discussed in v4. That the device fills the probe buffer with zeroes is now a "SHOULD" instead of a "MAY", since it's the only way for the driver to know