Displaying 20 results from an estimated 12366 matches for "resetes".
Did you mean:
reseted
2007 Nov 26
0
14 commits - libswfdec/swfdec_as_object.c libswfdec/swfdec_file_reference.c libswfdec/swfdec_load_object.c libswfdec/swfdec_sprite_movie_as.c libswfdec/swfdec_system_security.c test/trace
libswfdec/swfdec_as_object.c | 64
libswfdec/swfdec_file_reference.c | 2
libswfdec/swfdec_load_object.c | 81
libswfdec/swfdec_sprite_movie_as.c | 19
libswfdec/swfdec_system_security.c | 1
test/trace/Makefile.am | 72
2017 Jul 20
0
[PATCH 000/102] Convert drivers to explicit reset API
On Wed, Jul 19, 2017 at 05:25:04PM +0200, Philipp Zabel wrote:
> The reset control API has two modes: exclusive access, where the driver
> expects to have full and immediate control over the state of the reset
> line, and shared (clock-like) access, where drivers only request reset
> deassertion while active, but don't care about the state of the reset line
> while inactive.
2017 Jul 19
7
[PATCH 000/102] Convert drivers to explicit reset API
The reset control API has two modes: exclusive access, where the driver
expects to have full and immediate control over the state of the reset
line, and shared (clock-like) access, where drivers only request reset
deassertion while active, but don't care about the state of the reset line
while inactive.
Commit a53e35db70d1 ("reset: Ensure drivers are explicit when requesting
reset
2008 Jul 13
3
Hard(?) lock when reassociating ath with wpa_supplicant on RELENG_7
Hi Sam,
do you know if there is anything done about cbb(4)? I have many
wireless adapters with ath(4), but only the one based on PCMCIA is
making problems on FreeBSD.
I cannot boot my notebook with the device inserted into the port, or it
will render the system unusable (100% load on cbb(4)).
And all I can see is the following:
Jul 12 14:58:39 link kernel: ath0: ath_chan_set: unable to reset
2020 May 14
2
[PATCH] vdpa_sim: do not reset IOTLB during device reset
We reset IOTLB during device reset this breaks the assumption that the
mapping needs to be controlled via vDPA DMA ops explicitly in a
incremental way. So the networking will be broken after e.g a guest
reset.
Fix this by not resetting the IOTLB during device reset.
Signed-off-by: Jason Wang <jasowang at redhat.com>
---
drivers/vdpa/vdpa_sim/vdpa_sim.c | 2 --
1 file changed, 2
2020 May 14
2
[PATCH] vdpa_sim: do not reset IOTLB during device reset
We reset IOTLB during device reset this breaks the assumption that the
mapping needs to be controlled via vDPA DMA ops explicitly in a
incremental way. So the networking will be broken after e.g a guest
reset.
Fix this by not resetting the IOTLB during device reset.
Signed-off-by: Jason Wang <jasowang at redhat.com>
---
drivers/vdpa/vdpa_sim/vdpa_sim.c | 2 --
1 file changed, 2
2018 Dec 31
5
[Bug 1314] New: nft reset quotas does not reset anonymous quotas
https://bugzilla.netfilter.org/show_bug.cgi?id=1314
Bug ID: 1314
Summary: nft reset quotas does not reset anonymous quotas
Product: nftables
Version: unspecified
Hardware: x86_64
OS: Debian GNU/Linux
Status: NEW
Severity: normal
Priority: P5
Component: nft
Assignee: pablo at
2012 Oct 18
1
PCI device not properly reset after VFIO
Hi Alex,
I've been playing around with VFIO and megasas (of course).
What I did now was switching between VFIO and 'normal' operation, ie
emulated access.
megasas is happily running under VFIO, but when I do an emergency
stop like killing the Qemu session the PCI device is not properly reset.
IE when I load 'megaraid_sas' after unbinding the vfio_pci module
the driver
2012 Oct 18
1
PCI device not properly reset after VFIO
Hi Alex,
I've been playing around with VFIO and megasas (of course).
What I did now was switching between VFIO and 'normal' operation, ie
emulated access.
megasas is happily running under VFIO, but when I do an emergency
stop like killing the Qemu session the PCI device is not properly reset.
IE when I load 'megaraid_sas' after unbinding the vfio_pci module
the driver
2008 Dec 10
3
rspecing rjs - form.reset(''form'')
Hello,
>
> I couldn''t find much info on this.
>
> How do you rspec this: page.form.reset("form")
>
> I looked in the have_rjs source code and I can''t find anything on form
> reset.
>
> Thanks,
>
> --
> Andrei
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2020 Mar 28
0
[klibc:update-dash] dash: mkinit: Split reset into exitreset and reset
Commit-ID: 7f799aacc75667708bafe8f4411891ec053d7d65
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=7f799aacc75667708bafe8f4411891ec053d7d65
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Sat, 19 May 2018 02:39:40 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:55 +0000
[klibc] dash: mkinit: Split
2011 Dec 30
1
PCI/VGA passthrough and function level reset (FLR)
I''m wondering if FLR really must be supported by the PCI card for
PCI/VGA passthrough to work or if it will work anyway. I have read in
the VTdHowTo that trying to pass through hardware without the FLR
feature will result in an error. At the same time I read on a pdf
document on the VMWare website
(http://www.vmware.com/files/pdf/techpaper/vsp_4_vmdirectpath_host.pdf)
that:
2020 Apr 16
0
[PATCH v2 7/8] tools/virtio: Reset index in virtio_test --reset.
On Thu, Apr 16, 2020 at 09:56:42AM +0200, Eugenio P??rez wrote:
> This way behavior for vhost is more like a VM.
>
> Signed-off-by: Eugenio P??rez <eperezma at redhat.com>
I dropped --reset from 5.7 since Linus felt it's unappropriate.
I guess I should squash this in with --reset?
> ---
> tools/virtio/virtio_test.c | 33 ++++++++++++++++++++++++++-------
> 1 file
2017 Dec 11
2
reset-brick command questions
Hi,
I'm trying to use the reset-brick command, but it's not completely clear
to me
>
> Introducing reset-brick command
>
> /Notes for users:/ The reset-brick command provides support to
> reformat/replace the disk(s) represented by a brick within a volume.
> This is helpful when a disk goes bad etc
>
That's what I need, the use case is a disk goes bad on
2020 Apr 17
0
[PATCH v2 7/8] tools/virtio: Reset index in virtio_test --reset.
On Fri, Apr 17, 2020 at 09:04:04AM +0200, Eugenio Perez Martin wrote:
> On Fri, Apr 17, 2020 at 12:34 AM Michael S. Tsirkin <mst at redhat.com> wrote:
> >
> > On Thu, Apr 16, 2020 at 09:56:42AM +0200, Eugenio P??rez wrote:
> > > This way behavior for vhost is more like a VM.
> > >
> > > Signed-off-by: Eugenio P??rez <eperezma at redhat.com>
2007 Dec 09
2
rake db:redo & rake migrations:reset - or how to cope with the change of db:reset
As many of you know, rake db:reset changed behavior just before Rails
2.0 got released.
db:reset used to drop the database, re create it and migrate it up.
The core team after integrating this feature, realized that it was not
used as intended and instead db:create now uses the schema.rb file
instead of the migrations.
Check the many discussions we had about this topic, you will quickly
notice
2015 Jan 06
2
[PATCH 2/11] memory: tegra: add mc flush support
On Tue, Dec 23, 2014 at 06:39:55PM +0800, Vince Hsu wrote:
> The flush operation of memory clients is needed for various IP blocks in
> the Tegra SoCs to perform a clean reset.
>
> Signed-off-by: Vince Hsu <vinceh at nvidia.com>
> ---
> drivers/memory/tegra/mc.c | 21 +++++++++++++++++++++
> include/soc/tegra/mc.h | 23 ++++++++++++++++++++++-
> 2 files changed,
2013 Jun 21
0
[Bug 696] Extra tcp options for REJECT --reject-with tcp-reset-both / tcp-reset-destination
https://bugzilla.netfilter.org/show_bug.cgi?id=696
--- Comment #3 from Alessandro Vesely <vesely at tana.it> 2013-06-21 15:50:56 CEST ---
(In reply to comment #2)
> you have to put this REJECT rule before any RELATED/ESTABLISHED
> conntrack ctstate match rules (which is suboptimal).
No, I can use conntrack -D to have the connection unESTABLISHED.
In general, it is polite to send a
2017 Jul 05
1
op-version for reset-brick (Was: Re: [ovirt-users] Upgrading HC from 4.0 to 4.1)
On Wed, Jul 5, 2017 at 5:02 PM, Sahina Bose <sabose at redhat.com> wrote:
>
>
> On Wed, Jul 5, 2017 at 8:16 PM, Gianluca Cecchi <gianluca.cecchi at gmail.com
> > wrote:
>
>>
>>
>> On Wed, Jul 5, 2017 at 7:42 AM, Sahina Bose <sabose at redhat.com> wrote:
>>
>>>
>>>
>>>> ...
>>>>
>>>> then
2006 Jan 09
1
Zaptel errors (power alarm?)
We've been having lost dialtone problems on one of our analog station
ports. Just before rebooting this time I noticed these in our dmesg
output....once the PBX comes back I'll get the times, but I can't help but
think this must have something to do with it. Anyone? Do we need to have
digium send us a replacement part?
Ouch, part reset, quickly restoring reality (1)
Power alarm