search for: boot1

...engine/device/base.c +++ b/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c @@ -2924,17 +2924,34 @@ nvkm_device_del(struct nvkm_device **pdevice) } } +/* returns true if the GPU is in the CPU native byte order */ static inline bool nvkm_device_endianness(struct nvkm_device *device) { - u32 boot1 = nvkm_rd32(device, 0x000004) & 0x01000001; #ifdef __BIG_ENDIAN - if (!boot1) - return false; + const bool big_endian = true; #else - if (boot1) - return false; + const bool big_endian = false; #endif + + /* Read NV_PMC_BOOT_1, and assume non-functional endian switch if it + * doesn't...

Dear R and S People: I have run across something very strange. Here is a function that I wrote for R: boot1 <- function(y,method="f",p=1) { n1 <- length(y) n2 <- n1*p n3 <- n2 - 1 a <- 0.5*(outer(1:n3,1:n3,function(x,y){n2 - pmax(x,y)})) return(a) } and here is the R output: > y1 [1] 9 8 7 3 6 > source("boot1.R") > boot1(y=y1,p=4) [,1] [,2] [,3] [,4] [,5...

Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..17676c75a 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++

Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..17676c75a 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++

Hi, Erin: A cleaner way is to pass "n2" to "outer" as a "..." argument, as in the following modification of your code: boot1 <- function(y,method="f",p=1) { n1 <- length(y) n2 <- n1*p n3 <- n2 - 1 a <- 0.5*(outer(1:n3,1:n3,function(x,y, n2.){n2. - pmax(x,y)}, n2.=n2)) return(a) } y1 <- c( 9, 8, 7, 3, 6) boot1(y=y1,p=4) The use of "assign" like this might be called "dir...

...in the config for SYSLINUX, etc. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- If, for example, you had two labels that only differed by the length of the label (a short name) or additional APPENDd parameters, this would reduce the amount of copies of the same configuration. LABEL boot1 KERNEL kernel APPEND initrd=initrd.img LABEL boot2 KERNEL kernel APPEND initrd=initrd.img extraParamForBoot2 could be shortened to LABEL boot1 KERNEL kernel APPEND initrd=initrd.img LABEL boot2 KERNEL alias.c32 APPEND boot1 extraParamForBoot2 I created this as I've got several instances of...

...hat there is an extra level (the subvol) which looks a lot like a directory. Since booting with the btrfs used works, I thought that it might be only a matter of configuration. To test this, I installed /boot into a btrfs subvolume. Post install, I then edited extlinx.conf to add the prefix /boot1/ to the /vmlinuz and /initramfs parameters. The installation included a mount point for the btrfs volume so I then ran: /sbin/extlinux --install /btrfsvol/boot1/extlinux and it responded with device on /dev/vda1. This looked like it should work but it did not. Instead I got a lot of &quo...

Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 27 +++++++++++++++------------ 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..37589f365 100644 ---

I seem to have partitions on two different disks with the same UUID: [tim at helen ~]$ sudo blkid /dev/sda2 /dev/sda2: LABEL="/boot1" UUID="5bbc8e95-6108-41f5-bc0e-5b5f8df5ce03" TYPE="ext3" [tim at helen ~]$ sudo blkid /dev/sdb2 /dev/sdb2: LABEL="/boot1" UUID="5bbc8e95-6108-41f5-bc0e-5b5f8df5ce03" TYPE="ext3" This is causing some confusion, as these are boo...

...tistic function? I thought "indices = sample(data, replace=TRUE)", but when I replaced "indices" with this command and used "boot", I got different results. Specifically, below are the codes for illustration. (1) The typical way by generating indices in the package: boot1 <- function (data, indices) { d <- data[indices] return(d) } AA <- c(1:10) require(boot) set.seed(123) results1 <- boot(data= AA, statistic=boot1, R=100) (2) The alternative way by calculating "indices" myself: boot2 <- function (data,indices) { indices <- sample(dat...

...u/nvkm/engine/device/base.c index 37589f365..c732074bf 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++ b/drm/nouveau/nvkm/engine/device/base.c @@ -2924,6 +2924,20 @@ nvkm_device_del(struct nvkm_device **pdevice) } } +static inline bool +nvkm_device_endianness(void __iomem *pri) +{ + u32 boot1 = ioread32_native(pri + 0x000004) & 0x01000001; +#ifdef __BIG_ENDIAN + if (!boot1) + return false; +#else + if (boot1) + return false; +#endif + return true; +} + int nvkm_device_ctor(const struct nvkm_device_func *func, const struct nvkm_device_quirk *quirk, @@ -2973,13 +2987,15 @@ nvk...

.../engine/device/base.c > @@ -2924,17 +2924,34 @@ nvkm_device_del(struct nvkm_device **pdevice) > } > } > > +/* returns true if the GPU is in the CPU native byte order */ > static inline bool > nvkm_device_endianness(struct nvkm_device *device) > { > - u32 boot1 = nvkm_rd32(device, 0x000004) & 0x01000001; > #ifdef __BIG_ENDIAN > - if (!boot1) > - return false; > + const bool big_endian = true; > #else > - if (boot1) > - return false; > + const bool big_endian = false; > #...

...start storage config looks like this: bootloader --location=mbr --driveorder=sda,sdb zerombr ignoredisk --only-use=sda,sdb clearpart --all --drives=sda,sdb part raid.boot0 --size 1000 --ondrive=sda part raid.swap0 --size 8192 --ondrive=sda part raid.root0 --size 8000 --grow --ondrive=sda part raid.boot1 --size 1000 --ondrive=sdb part raid.swap1 --size 8192 --ondrive=sdb part raid.root1 --size 8000 --grow --ondrive=sdb raid /boot --fstype ext4 --device md0 --level=RAID1 raid.boot1 raid.boot0 raid swap --fstype swap --device md1 --level=RAID1 raid.swap1 raid.swap0 raid / --fstype ext4 --device md2 -...

HI, i have updatete to 6.1-PRERELEASE and after the "installworld" step GRUB is unable to boot FreeBSD. After i did the installworld and rebooted the GRUB error was: 23 : Error while parsing number I have reinstalled the standard FreeBSD loader for now. Booting with a GRUB boot-floppy i am able to start either XP or Linux but trying to start FreeBSD the system just reboots, no

...om32/samples or com32/modules, depending on where H. Peter Anvin feels it is most appropriate. If, for example, you had two labels that only differed by the length of the label (a short name) or additional APPENDd parameters, this would reduce the amount of copies of the same configuration. LABEL boot1 KERNEL kernel APPEND initrd=initrd.img LABEL boot2 KERNEL kernel APPEND initrd=initrd.img extraParamForBoot2 could be shortened to LABEL boot1 KERNEL kernel APPEND initrd=initrd.img LABEL boot2 KERNEL alias.c32 APPEND boot1 extraParamForBoot2 I created this as I've got several instances of...

...ybe not to y'all I use clamscan --exclude in other places but this certain one will not work... let me put up my fstab before I explain k: # This file is edited by fstab-sync - see 'man fstab-sync' for details LABEL=/ / ext3 defaults 1 1 LABEL=/boot1 /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 LABEL=/rbbu /rbbu...

...lassyear1[i]==3)),ncol=3) abs(eigen(mat,only.values=T)$values[1]) } Now, in the pooled matrix from all years I would like to sample in a way that the number of bootstrap samples taken from each year is equal to the number of data points from each year. Therefore I'm defining strata=year. boot1 <- boot(myfile, mat.fun, 5000, strata=myfile$year); boot1 Is this the correct way to do it or did I misunderstand the strata-argument? I checked in Davison, A.C. and Hinkley, D.V. (1997), but I'm still not quite sure. Thanks very much in advance for your help! Sincerely, Saskia Sandring...

I did a clean install of centos4.2 and i noticed on boot up that my mount points had a "1" added to each. For example here is a snippet of my /etc/fstab: /1 ...... /boot1 ...... /var1 ..... of course just what is pertinent to the problem is listed?

Hi!!! I am trying to run a bootstrap but I have troubles. My code is as follows theta <- function(x){mean(x,)} boot1<-boot(x,theta,R=1000) Error in statistic(data, original, ...) : unused argument(s) (1:487) Any help is welcome Thanks [[alternative HTML version deleted]]

...r regression, the following code works. library(nlme) data(Soybean) fm1.nls <- nls(weight ~ SSlogis(Time, a, b, c), data=Soybean) summary(fm1.nls) bstat <- function(A, indices) { mboot <- nls(weight ~ SSlogis(Time, a, b, c), data=Soybean[indices, ]) return(coef(mboot)) } require(boot) boot1 <- boot(Soybean, bstat, 2000) boot1 For nonlinear mixed effects models it doesn't work. > stat.nlme <- function(A, indices) { + boot.nlme <- nlme(Gdiff/0.5 ~ SSlogis(tmmean,a,b,c), + fixed=list(a+b+c~1), + random = list(a+b+c~1), data = Soybean[indices,]) + return(fixef(boot.n...